Not long ago I bought Seven Languages in Seven Weeks from the Pragmatic Bookshelf (electronic, of course ;-) with the sole aim of learning new languages I can then exploit to produce code in myriad forms and shapes. I asked in Twitter for recommendations of books that a geeky developer like me should read and
A while back I had the idea of bringing the concept of Acceptance Test-Driven Development into our department, where we mostly maintain an existing, pretty large, mature and complex solution. The conclusion after my presentation and following discussions was that we already do it, at least partially (as I mentioned in this comment). With this
I’m going to give an introductory presentation about Acceptance Test Driven Development to our R&D unit next week. I’ve been harvesting the Internet for experience reports of applying ATDD to legacy systems to no avail. There are lot’s of basic presentations about it but nothing deeper and nothing regarding legacy code bases. So, with the
With thanks to Esko Luontola I now have a pet project. It’s called Dimdwarf. A direct descendant of RedDwarf but with some additional finery (the biggest difference being that managed references are invisible to the developer). The project was written in Java (some helper scripts with Ruby) but all the new code is written in
Many have gone through the agony of a Scrum transformation and noticed that revolution is hard. It requires a lot from the people involved but at the same time it is mostly adapting to new surroundings, to the new way of collaborating and making work visible. Agile methods come with the implicit expectation that you
Heading to bed, taxi to airport leaves in 6 hours. I’m so excited :-). I just hope my luggage clears Charles De Gaulle airport so that I have clothes when I arrive in Kuala Lumpur. I’ll try to update my blog with my feelings during my stay in KL. Stay tuned!
The essence of a continuous integration is that the system is regression tested all the time people develop and commit new features or bug fixes. The basic assumption is that the code is always tested for regression on multiple levels; unit, component and system/integration level. This leads to an interesting question: Can you really have