Things I have learnt over time ...

Technical debt is like Tetris

Published on 
1 min, 108 words

This article uses a really neat analogy with Tetris for illustrating the impact of technical debt. Leaving gaps is akin to leaving technical debt in the code base and makes subsequent changes more difficult or slower to ship.

Read more ...

How to run a planning workshop

Published on 
4 min, 677 words

We have just completed a two week exercise with the whole development team to identify, design and estimate the next phase of work. It started as an organic process as we found the best way to do this and then developed into a repeatable process for the latter functionality.

Read more ...

Categories: work

Places to name things

Published on 
1 min, 33 words

This one is just for future reference for me that I may find useful one day - a website full of resources that may be useful for naming things.

Read more ...

Categories: business

The value of throwing code away

Published on 
1 min, 161 words

We had a discussion at work about "throw away" code. One of our developers was very against developing any code that would be thrown away afterwards. He referred to this as a waste. In my view sometimes the biggest gain can be in developing code that is meant to be thrown away. It can be used to try things and, more importantly, learn things that can shape the code that is kept. This article sums it up much more eloquently than I can.

Read more ...