Now, I've preached the unit testing gospel in theory for a while now, but experiencing it in practice is a different matter entirely. Boo has automated tests, but they're really mostly integration tests and I always wrote them after finishing everything else. But today, in an underground coding session, I --
( did some stuff that you can only find out about if you look inside and by now you're too curious so there's really no escaping it now is there? )

I've recently re-ran into some of my old code which animates rows in a .NET DataGridView. I know trying to do animation in WinForms is close to pointless, what with WPF and everything, but it was there and we don't have WPF at work yet and I needed something fun to toy with. Bear with me ( Read more... )

Lately we've been semi-scrumming in the section. We tried to integrate some of the Scrum practices, while ignoring others (the hard ones, you know, like the ones that require management commitment and stuff like that). This isn't so healthy, I know, since the practices were designed to work together; but we're trying to use a sensible subset, in an ( Read more... )

Typical meeting at the section. There's the project manager, the dev lead, the lead tester and me, functioning as the system designer. We're there to solve a problem.

( Sounds like a joke, right? Well it isn't. )

Today I found myself explaining to a new guy over at the other section (the one we don't get along with very well) why Agile software development works way better (at least for us) than the conservative waterfall model (what they have been using for the past eternity and believe is the only 'right' way to do things ( Read more... )