OddThinking

Here is a software analysis anti-pattern I have seen many times in my career. It is popping up in my current project, and I am trying to work out how to subvert it early.

Today, I am justifying a particular personal coding standard rule. If I explicitly argue the case, I hope I will conform to it more.

I have decided to abandon screen, and am returning to having to re-login each day.

I am filing this under “I am doing Linux wrong, but I don’t know where.”

A whinge about my server host.

Here is a short, fictionalised, autobiographical play I wrote, in which unit-tests cause more technical debt than the code.

One of the many reasons I have been quiet recently is I am working on a personal project – an amateur stop-motion video. The final product will appear to be a large group of my friends playing music in an orchestra. The raw material I have is dozens of sets of still photos of my friends pretending to play instruments in front of a green-screen. Each set has about 10 photos of the person playing the instrument.

I am working on an interesting challenge, and I thought that I might benefit if I wrote it out as a blog article to force me to think it through.

Tying together the Nonblocking Log Handler story.

In which Julian attacks weight-loss supplements, Agile development, TV show segues, Chaos Theory and Economics, just so build up enough momentum to attack a much-beloved (by him!) computer science legend about something he wrote over 20 years ago.

What my current project has taught me about refactoring:

Here are the specs for a great weekend project that I don’t have time for, that would improve my cross-development productivity.