Don't worry, this isn't one of the lame April Fool's jokes that have been infecting, well, just about everything I've read so far today. If you'd like to just read about the interesting ones, the Washington Post has a roundup of the online jokes (via Tech Review). Oh, and my favorite joke of the day has to be this bit from the Library Journal: "Degree in “Google Science” Offered by Syracuse I School."
Now that we've dispensed with that little bit of unpleasantness, on with the show...
Go check out Jamis Buck's description of of Test-First Development. His post makes me even more interested in this. Like him, I'd dabbled in it before, just a bit. And, like him, I found it pretty cool. And, like him, I generally just dive into a project and play around with things until I get them right. So, like him, I should probably start to make a concerted effort to do test-first development. So should you, too.
One question: if you're a newbie, just learning to program, or just learning the language, would the test-first approach work? When I'm at this stage (now, learning a new language), I'm often so clueless I wouldn't know where to start. I suspect that doing tests would provide one with a good framework as they learn (as well as a safety net), but I'm not sure. Anyone out there ever start from scratch with this approach?
(How was that for a post on two different topics that had NOTHING to do with each other??)
Posted by Karl
April 1, 2005 10:34 AM