Interpreted Dance

It’s a weird exciting time in software engineering.

LLMs and coding agents like Claude Code crank out code but have poor taste.

Sometimes I finish a session in Claude Code and run the /cost command.

A few sections of this were written by an LLM, before I discovered my opinions on LLMs for writing assistance.

A handful of pieces of great software writing float around in my brain.

Lately I’ve been thinking about possibilities and capabilities on engineering teams.

My Twitter feed is a nightmarish cacophony - cute art, police brutality, security vulnerabilities with catchy nicknames, dire economic news, fun jokes, squabbles over programming languages, etc.

My motorcycle goes about 140 mph, and gets there pretty quickly.

I manage a team developers.

Keep interfaces small.

I recently took six weeks of paternity leave.

Screwing up hurts.

A while ago I read a post that included the following quote: Each hour spent on code review saves 33 hours of maintenance.

I read a fair amount about engineering management or things tangentially related to it.

Recently I’ve been teaching networking concepts to front-end developers.

I co-host a podcast, Soft Skills Engineering, with my friend Dave Smith.

I just got back from Deconstruct Conf.

A bug report has three main parts: what you expected to see, what you saw and steps to reproduce.

Here is a typical interaction I see with new hires at every place I’ve worked.

I’ve been a professional developer for about a decade, but there are tons of things I still don’t know.