I’m Justin, a software engineer. For a long time I wrote Java, and lately I’ve been learning Go, writing Kubernetes operators, and falling down PostgreSQL rabbit holes on Sunday nights.

For years I thought the hard part of the job was the technical problem. I’ve come to think it’s usually something else: framing the problem so everyone agrees on it, explaining a trade-off without hiding behind “it depends”, and changing someone’s mind (or letting them change mine).

That matters more now. AI can write a lot of the code and answer a lot of the questions. It can’t sit in the design review and decide what we should build, and it can’t make a tired team understand why. People still have to do that part.

What this site is

  • Let’s Talk Software: short episodes where I practise explaining one idea clearly. I ask a question, make a prediction, run the experiment, and explain what happened.
  • Writing: longer essays, both technical deep dives and notes on how engineers think and talk.
  • Workbench: the hands-on side, with system design notes, a Kubernetes lab, and coding patterns.

What I believe

  • If you can’t explain it simply, you don’t understand it yet.
  • A good question is worth more than a fast answer.
  • Trade-offs are a conversation, not a verdict.
  • Technical depth is what earns you the right to be listened to. Clarity is what gets you heard.

Say hello

The best way to follow along is the RSS feed.