There’s been a crazy fog of speculation surrounding my previous employer for the past few years, and I’ll admit I’m guilty of contributing. Many of Nokia’s moves during that time have been unusual, counterproductive and even downright bewildering… so it’s hard to blame anyone for wondering what the heck platform-torching CEO Stephen Elop has really got in mind.
Planet maemo: category "feed:a7ebd5f9cfd7ca3830cb6317611d7f18"
When I was a kid, the most exciting Christmas gift my parents got me was a green Honda QA50 mini-bike. Until I was upgraded to a cooler Honda Z50 a few years later, I rode the hell out of that little thing. Even stripped a great deal of skin off my 9-year-old body the first day riding– then got right back on, to my mother’s horror, and kept going.
A friend of mine in the MeeGo community brought my attention to an interesting concept he calls MeeGoVerse, which translates common gaming elements to real-life work as a sort of “massive multiplayer” endeavor. One important aspect is the use of achievements to reward people for attacking necessary community evils, like bug reporting. I can envision Meegon badges for each achievement. People love to contribute, and especially be recognized for it.
I wrote in May of last year asking, only partially rhetorically, if this would be a make-or-break year for consumer electronics giant Nokia. And like many other pundits, I’ve offered my previous employer sound survival advice on more than one occasion [1][2][3] . Based on recent financial reports, nobody listened.
I’m going to confess something that’s likely to cost me Twitter followers, kill future career prospects and launch a mild Comment war:
Want to stop productive bug reporting in its tracks? Want to get the trolling rolling? Toss a flaming “Works for me!” into the mix and stand back.
I’ve often described the title of this piece as the most devastating insult one techie can inflict on another. It’s surely one of the more popular. And while in many (maybe most) cases it’s dropped in perfect innocence, this little innocuous phrase tends to land with the force of a nuclear bomb.
Bug triage is a progressive process. After the initial report, others join in to share their experience and a living, breathing, sometimes-viral organism develops. Those afflicted with the bug take co-ownership of the report, as do those working to resolve it. They may see anyone poking in to coo a cavalier “works for me!” as an affront. A theft of discourse and productivity. And a blatant example of trolling.
It’s especially an issue in open source communities, where much if not all of the work involved is strictly volunteer. Pointless infringements on precious time are not taken lightly. And unless the poster is a sociopath, they surely don’t want to develop a troll’s reputation.
But what if the alleged agent provocateur really is innocent? There’s actually value in the remark if it’s sincere. A valid “works for me” becomes a control, an example of an environment or set of conditions where the bug has failed to manifest. A bug-free control can aid in troubleshooting by enabling investigators to better identify critical environmental differences. In fact the more “works for me” contributions there are, the quicker the culprit can be identified. It lurks in the unique shadows of the bug originator’s domain… and can often be something really simple.
Obviously bug triage depends on collaboration and, to some extent, healthy competition. But successful bug resolution is best accomplished by avoiding ego-driven contributions on either side. That means no taunting, and no rash assumptions. Consider your words carefully. If you have no stake in the bug, just observe from the sidelines if at all. And if personality conflicts emerge, they’re best taken out of the bug stream and handled between the adversaries.
Keep on (de)bugging!
Filed under: Delivering Quality, Mentioning Maemo, Mentioning MeeGo, Smooth Codings, The Cat Corral, The Write Stuff, Unusability, Views and Reviews, Ways of Rocking Tagged: bug, debugging, forumnokia, LinkedIn, triage
My third Nokia N900 lost the ability to recognize a SIM card recently. And the usual home repair tactics (bending the SIM, adding padding between the SIM slot and battery) had no effect. I tried a cold reflash to no avail.
So I went back to my previously-trusty Nokia E71x only to find that the infrequent odd behavior it had been exhibiting (mainly going unresponsive when I needed it most) has now become the norm. The little thing spends most of its time now in a coma and requires measures just short of serious abuse to awaken. Factory reset didn’t help there, either. It’s also not a mobile computer.
I’ve been blessed with Nokia N8 and E7 devices thanks to Nokia’s Developer Champion (formerly Forum Nokia) program, but those ended up in the hands of my two young sons and good luck getting either back. Despite adult reviews to the contrary, my teenagers love the things (their friends are actually jealous).
So I need a new phone. Fast.
As I wrote yesterday I am (almost completely) enthralled with the MeeGo-ready Nokia N9. Not the drama developing around it, for sure, but the device itself.
But it’s not out yet, and even if/when it’s made available I don’t expect to see it in the US any time soon. Nokia apparently has a similar handset in the wings meant for Windows Phone 7, and it’s clear now that the two products will be launched in mutually-exclusive markets. Even if the N9 makes it to the US, I won’t be able to afford it thanks to a severe reduction in salary since falling out of the Nokia nest and I doubt I’ll see this subsidized (although there are rumors of an AT&T offering at some point).
I’m tempted to turn to the AT&T store to grab something there. In fact I even went so far recently as to purchase an HTC device, but the server choked on my order. There’s some karmic irony in that, no doubt.
There are still some legacy Nokia phones gathering dust in my house. My oldest son has an N93 that was never used since Nokia inexplicably chose to support T-Mobile bands but not AT&T’s. I also have an E70, which I believe Nokia should resurrect with some modernization. I think we have an old candy bar or two lurking somewhere as well.
I really, really miss using my N900 though. Regardless of its faults, toting a mobile computer with cell radio capability worked best for me. Hmmm… maybe what I really need is one of those N950 developer devices…
Filed under: Mentioning Maemo, Mentioning MeeGo, The Write Stuff, Unusability, Views and Reviews Tagged: AT&T, forumnokia, LinkedIn, N9, N900, N950, Nokia
Leave it to a crafty Nokia press event announcement and a 49-character burst from a long-dormant Twitter account to fire up the imagination of the collective MeeGo and Maemo communities– especially the latter.
I’ve posted before about Nokia’s shaky prospects for this year, and the need for the first official MeeGo device to launch big. Based on the caginess around this event, I think Nokia’s PR folks are getting it– “it” being a launch management system close in form to Apple’s own. Of course we need to watch the event itself to see if the hype and hope aren’t squandered.
Speculation is running wild over what will be announced, but Nokia has promised it will be “disruptive”. That could manifest in so many ways I’m not going to bother exploring them here… instead, I’m going to wait the 2-and-a-half hours for the actual event and start twittering as it develops. Just follow! I’ll post a wrap-up here sometime afterward.
Update: add an hour to that countdown. I hear the event is delayed.
Filed under: Mentioning Maemo, Mentioning MeeGo, Ways of Rocking