Skip to main content

· 4 min read
Webber
Software engineer

A common approach to working with coding agents is to hand them a prompt and hope for the best. Another is to first make a plan or specification. In both cases, unresolved ambiguities and assumptions often remain hidden until the code appears, and by then it is harder to change.

What if the spec becomes the source of truth, and we can incrementally improve it using specialised agents?

· 21 min read
Webber
Software engineer

Always wanted your terminal to look and function like that of a professional developer? This post is my attempt at providing a concise guide to setting up a modern terminal, while explaining essential terminology and decisions made along the way.

To make for a truly slick experience, I have considered different terminals, shells, prompts and hotkeys, as well as command-line tools and plugins, including typeahead and fuzzy search.

· 4 min read
Webber
Software engineer

While ordering parts for my new energy efficient server, I ended up buying a second hand I7 9700K processor.

When the piece had arrived, I was surprised to see a chunk of dirt that was burnt in, seemingly connecting some contact points together. I was worried that this would cause a short circuit and damage the CPU.

· 12 min read
Webber
Software engineer

For some developers choosing the right stack for an application may seem like a trivial task; simply follow best practices and choose the most modern well-supported tools out there.

While this approach will usually lead to a successful outcome, I've found that spending just enough time up-front has led me to create working products much faster and with less effort.