coding

Reducing Build Size

Published on 
1 min, 161 words

I have been developing a Maui application as a side project and on the whole it has been a fun process. It is still very buggy and there are some pain points however it seems to work. One aspect I haven't liked is the size of the build artefacts - they are huge if you have multiple projects.

Read More

Categories: coding

Lazy programmers can be the most productive

Published on 
1 min, 129 words

There is often a work culture that you should be busy all the time - if you are a programmer you should always be typing and producing code. Programming is a mental process and so requires thinking. Sometimes a little thought upfront saves a lot of pain and work down the line.

Read More

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

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