Two steps to become agile

A lot of companies today wants to become “agile”. The $100.000.000 question is: How do you become agile?


Elastic-, plastic- and fracture characteristics of code

I recently had a post about technical debt, and Jelena made a very insightful comment that it was like elastic, plastic and fracture characteristics of materials like steel. I started to comment on the comment, but eventually I thought it deserved its own post. More

Where is software quality going?

Yesterday I was visiting Scania when their R&D department had a family-day where they demonstrated what they are working with. Scania, for those of you who don’t know, is famous for making high quality trucks and buses. What struck me when we went from room to room and hall to hall was that wherever we went, there was an automated testing rig!


“Manual processes are risks”

The other day I heard a person on my project say “Manual processes are risks”. Generally, if you do something that has a risk, you want to have a chance to gain something from taking the risk.


Refactor towards abstraction

I have been in discussions about how far to refactor a lot of times. “Until duplication is removed”, is a common position, and sure, that is fine.


Agile is relative and dynamic

Some people say things like “I wonder what will be the next hype after Agile?”.

I my opinion this illustrates a misconception about agile, that agile is static and absolute. This is simply not the case.


Refactoring organizations – refactoring code

Today I was struck by the similarities between rewriting code (as opposed to refactoring it) and how many companies reorganize.

When I was a young programmer and the code I had written was a mess I thought that if I just got the chance to rewrite everything it would then work better. Out with the old, and start on a blank sheet.


Previous Older Entries