The Coding Craftsman

If this image is to be believed, one of the problems of being a coder is that your screens are too far apart, and some of them are the wrong way around.

Don’t panic.

It just took me four attempts to write an if statement.

“Oooh, this is a bit half-baked” – it’s a saying that’s been coming up a bit recently.

In the handover of a particular side-project that I resigned from, I was asked to productionise the logging, so I wrote a special logger, which randomly added messages to the output.

This is an index of articles I’ve written debunking things people think are mandatory for agile, and suggesting alternatives.

Nobody likes it when I make music with AI.

It’s nice to be finding more variants of the Test Smells I have been writing about over the last few years.

For every action, there’s an equal and opposite.

When writing code, test first, we focus on the observed behaviour of the code based on states we can put the system in before trying the code out, and the final state of the system or the outputs of the code.

I want to talk about this LinkedIn comment: It’s based on the reasonable hypothesis that if you provide good guardrails against bad AI code, then you’ll not get bad code, so don’t need the bottleneck of manual code review, allowing you to focus on specifi…

In software development, things are either boolean, or they’re not.

You’re going to have to read this in the inner monologue voice of a hard hardboiled detective.