There's only so much time, and much of it is wasted. I'm going to try to waste less of it by means of this cunning plan:
I'm unsubscribing from some RSS feeds and subscribing to some others.
I threw out the MacDailyNews feed a while ago, and it felt quite liberating. Today I've gone further. MacWorld, MacUser, TUAW, AppleMatters etc, in fact, the whole folder called 'Apple News' has been chucked.
I'm thinking of chucking 'Tech News' too (The Register, Wired, Ars Technica), but haven't plucked up the courage yet.
The feeds I'm subscribing to are all blogs. They're blogs by professionals software testers. It's what I do, but I don't think much about it, I don't read much about it, and I'm not really getting any better at it. I want to. Pretty much all the books I've read on testing cover the same old stuff and are, frankly, uninspiring.
So I'm looking to real people for inspiration instead. Wish me luck.
I'm starting with Adam Goucher's Quality through Innovation and Eric Jacobson's Test This Blog. I'm going to use them to learn from and I'm going to use them as experienced content filters.
Saturday, 10 July 2010
Monday, 21 June 2010
Cognitive dissonance holds no fears for him.
Charles Arthur calls Paul Thurrott an idiot very politely.
Thursday, 17 June 2010
Blog Comments
I'm not a tech blogger. I'm a Software Tester and I occasionally post, occasionally about tech, because it's good indulgent creative fun and, as pretty much nobody reads this, it's not going to hurt anyone.
This post was going to be a comment on Ian Betteridge's blog entry on the whole should-Gruber-allow-comments-on-Daring Fireball thing.
As Ian wants to encourage everyone who really wants to comment on what I write to get their own blog fired up, and write. You never know, you might enjoy it, that's what I'm doing.
It's not, though, the first time I've written here as a response to another blog. I do use comments on sites, but not really very much these days. It seems like a waste of time and effort. There's an awful lot of stupid out there and I'm trying not to participate.
I'd tend to use Twitter to contact @ianbetteridge, who I kind of know, via Twitter, and I'd use email to contact comments@daringfireball.net. @gruber doesn't know who the fuck I am, and as emailing is more effort, I'm only likely to do so if I have something to say that I think he'd want to hear. I honestly don't want to waste his time.
I'd probably email John if I thought he'd got something factually wrong. He'd want to correct it, (which he does). I might also drop him en email if I thought he'd missed something (say he was writing about drawing graphs, but seemed not to know about omnigraphsketcher, and I thought that was a great tool he should know about).
The first post on this blog linking to an external source linked to Daring Fireball. That's no coincidence. Had there been comments, I'd have left one alongside dozens of others that would be ignored and forgotten.
So thanks, John and Ian for indirectly and directly getting me to post stuff here that at least I'll be able to read again sometime.
This post was going to be a comment on Ian Betteridge's blog entry on the whole should-Gruber-allow-comments-on-Daring Fireball thing.
As Ian wants to encourage everyone who really wants to comment on what I write to get their own blog fired up, and write. You never know, you might enjoy it, that's what I'm doing.
It's not, though, the first time I've written here as a response to another blog. I do use comments on sites, but not really very much these days. It seems like a waste of time and effort. There's an awful lot of stupid out there and I'm trying not to participate.
I'd tend to use Twitter to contact @ianbetteridge, who I kind of know, via Twitter, and I'd use email to contact comments@daringfireball.net. @gruber doesn't know who the fuck I am, and as emailing is more effort, I'm only likely to do so if I have something to say that I think he'd want to hear. I honestly don't want to waste his time.
I'd probably email John if I thought he'd got something factually wrong. He'd want to correct it, (which he does). I might also drop him en email if I thought he'd missed something (say he was writing about drawing graphs, but seemed not to know about omnigraphsketcher, and I thought that was a great tool he should know about).
The first post on this blog linking to an external source linked to Daring Fireball. That's no coincidence. Had there been comments, I'd have left one alongside dozens of others that would be ignored and forgotten.
So thanks, John and Ian for indirectly and directly getting me to post stuff here that at least I'll be able to read again sometime.
Wednesday, 9 June 2010
Ten reasons why you should still avoid Android
1. The back of the case is still plastic, so it's going to get scratched to buggery and the battery cover will keep falling off.
2. Hardware designed to meet a features checklist with no regard to usability.
3. The camera will have a tiny sensor with a huge megapixel count, which will yield awful noisy images.
4. You can't upgrade the OS to the latest version because the carrier doesn't let you. You have to buy a whole new phone and get locked in to another lengthy contract, probably getting a lower 'unlimited' data cap in the process.
5. New Android devices will be out practically every week, rendering your Android device out of date, forcing you to sell it at a loss in order to upgrade to the latest and greatest and get locked in to another lengthy contract, probably getting a lower 'unlimited' data cap in the process.
6. Locked in to Google for map data, which means directions will probably tell you to walk across a busy road and probably die. Add the cost of good health insurance to that mobile contract.
7. Voice-to-text that you'll have to correct manually, which will take more time, so you won't bother after a while. Even if it does work, which it won't, which I can say with complete certainty, even though I've never used it on a phone, you won't use it becasue it'll make you look like a dick in public*
8. Doesn't have a gyroscope, so gaming is impossible. It'll still be impossible when a gyroscope is introduced, because it didn't have one to start with, and no games will support it. Ever.
9. Due to uncontrolled multi-tasking, your battery will only last for 30 minutes, and you'll have to use a clunky task manager to take control, but the battery will be dead by the time you notice anyway.
10. See the web grind to a halt with all that Flash crap.
Yes. That was mostly bullshit. Want Android ? Get an Android device. Want an iPhone ? Get an iPhone. Happy with your crappy PAYG 4 year old mobile and can't justify the contracts on any smartphone ? Stick with that phone. Honestly, it's fine.
* If you use a BT headset, you don't seem to mind looking like a dick in public, so this may not apply to you, except it will, because voice recognition doesn't work. I know this for certain because I bought some in 2000, for a desktop, and it was shit. It didn't work then, and itll never work. That's crazy Star Trek tech. Science *Fiction*.
2. Hardware designed to meet a features checklist with no regard to usability.
3. The camera will have a tiny sensor with a huge megapixel count, which will yield awful noisy images.
4. You can't upgrade the OS to the latest version because the carrier doesn't let you. You have to buy a whole new phone and get locked in to another lengthy contract, probably getting a lower 'unlimited' data cap in the process.
5. New Android devices will be out practically every week, rendering your Android device out of date, forcing you to sell it at a loss in order to upgrade to the latest and greatest and get locked in to another lengthy contract, probably getting a lower 'unlimited' data cap in the process.
6. Locked in to Google for map data, which means directions will probably tell you to walk across a busy road and probably die. Add the cost of good health insurance to that mobile contract.
7. Voice-to-text that you'll have to correct manually, which will take more time, so you won't bother after a while. Even if it does work, which it won't, which I can say with complete certainty, even though I've never used it on a phone, you won't use it becasue it'll make you look like a dick in public*
8. Doesn't have a gyroscope, so gaming is impossible. It'll still be impossible when a gyroscope is introduced, because it didn't have one to start with, and no games will support it. Ever.
9. Due to uncontrolled multi-tasking, your battery will only last for 30 minutes, and you'll have to use a clunky task manager to take control, but the battery will be dead by the time you notice anyway.
10. See the web grind to a halt with all that Flash crap.
Yes. That was mostly bullshit. Want Android ? Get an Android device. Want an iPhone ? Get an iPhone. Happy with your crappy PAYG 4 year old mobile and can't justify the contracts on any smartphone ? Stick with that phone. Honestly, it's fine.
* If you use a BT headset, you don't seem to mind looking like a dick in public, so this may not apply to you, except it will, because voice recognition doesn't work. I know this for certain because I bought some in 2000, for a desktop, and it was shit. It didn't work then, and itll never work. That's crazy Star Trek tech. Science *Fiction*.
Monday, 7 June 2010
Why I think Apple products are light on features…
Something occurred to me the other week regarding the paucity of box-ticking features on Apple products. I'd forgotten about that thought until reading a comment on Adam Banks' blog (Ten reasons to doubt the Telegraph’s linkbait). 1st draft of this entry was about 1,000 words. I've trimmed it a little:
Apple doesn't add any feature that introduces more problems that it solves.
Apple doesn't add any feature that introduces more problems that it solves.
Tuesday, 11 May 2010
#twitterjoketrial
The #twitterjoketrial reminded me a little of a story Mrs Daycoder told me recently. It's a case of procedures gone mad and common sense thrown out of the window.
Mrs Daycoder is a primary school teacher. She's trained in first aid. The school has an incident book, in which, according to procedures, all accidents and injuries must be recorded. The staff mostly have a reasonable amount of common sense, so below a certain threshold, very minor accidents and injuries simply aren't recorded. Once they make it into the book, then staff have no choice but to follow procedures to the letter.
One of the teaching assistants (TA) doesn't have quite as much common sense. She's a stickler for the rules. A child came in from the playground with a splinter in his finger. The TA immediately wrote it into the incident book, and procedures then had to be followed. The procedures forbid any medical treatment by staff, the child's legal guardian must be called in to deal with the incident, and this is what happened. The school secretary had to explain and apologise to the dumbfounded mother of this child that the staff weren't allowed to remove the splinter from her son's finger, and requested that she come to the school to deal with the incident. After convincing the mum that it wasn't a joke, she reluctantly came in. Had any of the other staff dealt with the issue at the start, they'd have done so without fuss and without the incident being logged.
The #twitterjoketrail is the same thing. At each stage, it came to the attention of someone who wouldn't or couldn't defy procedure for some reason. Perhaps through a legitimate fear of taking responsibility, a lack of common sense or pig-headedness.
That someone should have a criminal record, and have had his chosen career halted because of this should appall all of us.
Mrs Daycoder is a primary school teacher. She's trained in first aid. The school has an incident book, in which, according to procedures, all accidents and injuries must be recorded. The staff mostly have a reasonable amount of common sense, so below a certain threshold, very minor accidents and injuries simply aren't recorded. Once they make it into the book, then staff have no choice but to follow procedures to the letter.
One of the teaching assistants (TA) doesn't have quite as much common sense. She's a stickler for the rules. A child came in from the playground with a splinter in his finger. The TA immediately wrote it into the incident book, and procedures then had to be followed. The procedures forbid any medical treatment by staff, the child's legal guardian must be called in to deal with the incident, and this is what happened. The school secretary had to explain and apologise to the dumbfounded mother of this child that the staff weren't allowed to remove the splinter from her son's finger, and requested that she come to the school to deal with the incident. After convincing the mum that it wasn't a joke, she reluctantly came in. Had any of the other staff dealt with the issue at the start, they'd have done so without fuss and without the incident being logged.
The #twitterjoketrail is the same thing. At each stage, it came to the attention of someone who wouldn't or couldn't defy procedure for some reason. Perhaps through a legitimate fear of taking responsibility, a lack of common sense or pig-headedness.
That someone should have a criminal record, and have had his chosen career halted because of this should appall all of us.
Thursday, 8 April 2010
We Don't Need No Stinkin' Task Manager
I was in the pub last night. Sadly this doesn't happen enough these days, but there was a free meal in the offing, it wasn't £5.99 "chicken ding!", and it got me out of Fat Fighters this week. The conversation inevitably landed, at one point, on the iPad, and then meandered to the iPhone, then iPhone OS 4.0, and multitasking.
I pointed out that we don't know anything yet. All we know is that we have a date where 4.0 will be announced. That's announced, not released. New features, perhaps APIs and perhaps a new version of Xcode, but the OS itself will be released later.
What my colleagues actually want from multi-tasking, it seems, is not very much. Generally one additional thing, like Spotify/Pandora, or GPS tracking while running/cycling.
There was, thankfully, an acknowledgement that other devices that had no restraints on multi tasking were, frankly, shit, would grind to a halt, and require task managers to get things moving again.
This morning, I read no-multitasking-in-iphone-4-0, which sums things up quite nicely. This response "There may be some new audio API to allow Spotify in b/g, etc." makes a lot of sense. That would probably address 90% of complaints.
I was thinking that permitting a single background app would be OK, not just music. Suitable apps would have a low use background mode that would not exceed, say 5% of system resources, or however much the Music app currently uses when playing music in the background. Apps would qualify for background apps status during the approval process.
As useful as this might be, there needs to be a simply UI for managing this. The good news is that we already have it: start a task (like play some music), and quit the app. The app switches to background mode, and the foreground app quits, returning the user to the home screen. While the background app is running, a double-click opens a control to stop/pause/switch etc.
The bad news is that this isn't quite enough. I could have my GPS-tracking and Spotify running at the same time, but what happens when I quit the second qualified-to-run-as-a-background-app app ? How do I indicate to the user what just happened ? The options seem to be:
Finger-in-the-air, that probably covers 99% of case. Bump the limit to 2 running background apps, and this whole UI is broken. The extra 1% simply isn't worth the UI pain. We don't need no stinkin' task manager
I pointed out that we don't know anything yet. All we know is that we have a date where 4.0 will be announced. That's announced, not released. New features, perhaps APIs and perhaps a new version of Xcode, but the OS itself will be released later.
What my colleagues actually want from multi-tasking, it seems, is not very much. Generally one additional thing, like Spotify/Pandora, or GPS tracking while running/cycling.
There was, thankfully, an acknowledgement that other devices that had no restraints on multi tasking were, frankly, shit, would grind to a halt, and require task managers to get things moving again.
This morning, I read no-multitasking-in-iphone-4-0, which sums things up quite nicely. This response "There may be some new audio API to allow Spotify in b/g, etc." makes a lot of sense. That would probably address 90% of complaints.
I was thinking that permitting a single background app would be OK, not just music. Suitable apps would have a low use background mode that would not exceed, say 5% of system resources, or however much the Music app currently uses when playing music in the background. Apps would qualify for background apps status during the approval process.
As useful as this might be, there needs to be a simply UI for managing this. The good news is that we already have it: start a task (like play some music), and quit the app. The app switches to background mode, and the foreground app quits, returning the user to the home screen. While the background app is running, a double-click opens a control to stop/pause/switch etc.
The bad news is that this isn't quite enough. I could have my GPS-tracking and Spotify running at the same time, but what happens when I quit the second qualified-to-run-as-a-background-app app ? How do I indicate to the user what just happened ? The options seem to be:
- 1st background app continues to run, 2nd app just quits, user receives no indication.
- 1st background app quits, 2st app switches to background mode,user receives no indication.
- User gets a popup asking which one to run in the background
Finger-in-the-air, that probably covers 99% of case. Bump the limit to 2 running background apps, and this whole UI is broken. The extra 1% simply isn't worth the UI pain. We don't need no stinkin' task manager
Subscribe to:
Posts (Atom)
Posts
