Wow. That was easy. And fast.
Cool.
Wow. That was easy. And fast.
Cool.
Folks who read my old, earthlink-hosted blog via RSS will now see the posts from this new, improved, dreamhost-hosted blog. That’s because I just set up an automatic redirect from the old feed url to the new one.
So, welcome old readers. I’m alive and well, and working as a test architect for the Mozilla Corporation. After New Year’s, I’ll be ramping up my efforts to start testing projects involving the mozilla and other communities.
In the meantime, happy new year to you all.
p.s. I redirected the old feed to the RSS 0.92 version of the feed for this new site. You might want to subscribe instead to the RSS2 version or the Atom version if your feed reader supports it.
Thanks to a pointer from Bernie DeKoven, Samorost2.
Late last night, I skimmed through the first 7 chapters of Michael Feathers‘ book Working Effectively with Legacy Code, and came up with the following quick action items:
I’ve come to accept these late-night inspirational yet confusing thoughts.
Earlier this evening, I learned that Danny Faught is putting together a toolsmiths guild/group/something (details to be shared in the future). I read over the archived discussions, and realised that I want to be a toolsmith for the mozilla community.
But the community is huge, so I should find other toolsmiths. Or attract them. Or grow them.
But I also need to find programmers and testers who are in need of toolsmith services.
I should be an example of what I think a toolsmith should be. But time spent being a toolsmith is time not spent growing a toolsmith community. And I think I’m better at growing the community than being an exceptional toolsmith. But I still need a body of work (running code) to point to when I talk with others about these ideas.
Balance. Bias towards running code. Vertical slices of functionality. Start with something doable, then improve incrementally and by factoring and refactoring.
But ARRRRRGGGGGGGHHHHHHH! I need to pick something and get coding. Something besides security testing, because I will need to share the results with as wide a community as possible.
Maybe Calendar or XForms, since developers from those areas have said they’d like to work with me on tests. Or Places, since they have a test script that looks like it would be easy to convert to a standard harness. Or something else that will enter my awareness.
Sigh. I’m done whining now.
I’ve created a Software Testing project coordination page just to get things started.
One part of writing is writing things down, and the page is not much more than that. One step at a time.
I’m dutifully following the protocol and staying home today. But I’m having trouble getting started on anything ecept the most trivial of next actions.
Maybe I should run a dash.
The laptop is going to live in the home office over the holiday weekend, so expect fewer posts from me until Tuesday.
Scott Kveton is profiled in this Information Week article.
I met Scott when he came down to visit moco HQ in November. He’s a nice guy, and an old unix-head (like me).
I owe him an email describing a few projects I hope some grad students might take on.