A developer’s status update: Test driven deadlock

No worries, I do value testing. But test driven? It depends.

The last few weeks I’ve been working off and on building a crawler. The thing triggers a series of scheduled tasks that could run in parallel, generating (possibly) tasks (that are consequently scheduled again in their own task-specific queue) on its own and so on. The end goal is structured copies of external resources (read: webpages). But I’ve been stuck close to the start for quite a while, setting up the base architecture using the test driven development approach. And I’m failing, it’s going too slow :(

Small victories

Like many developers, this is not my first parser/crawler. But this time I wanted to make a GoodParser™. Make it more extensible, and flexible and foremost robust, building in fault-tolerance from start. But I’m not getting near the end result and it is frustrating.

The TDD-school says make small victories, and oh yes, I had my sheer number of victories already. But the end is nowher…

I'm still writing...

I started this blog with a simple plan in mind: every now and then I have been coming up with an idea that seems to be interesting enough to think about a bit more. Such ideas, I thought, should be worth sharing…… and now I discover that most of my quick writeups aren't that good anyhow… or at best dated. I committed myself to posting only something that is good enough to post (and of course long delays between posts may force myself to lower this 'quality standard' (you're reading a good example)). So work is in progress, but I've got other things to do (planned date of graduation is getting close… quite close :o ) Just subscribe to the feed. That's what feeds are for :)