Fred Lackey ·

Writing

Notes on software craft, fatherhood, and the long game of building things that last. Arranged chronologically, newest first.

2026

The Compound Returns of Boring Architecture

Why the most productive codebases I have ever worked in were relentlessly dull, and what that teaches us about the seductive trap of premature abstraction.

On Naming Things with Precision

A variable name is a micro-essay. It must compress intention, scope, and type into a handful of characters. Here is how I approach the problem after twenty years.

Twelve Years of Node: A Retrospective

From my first Express route handler in 2014 to modern runtime wars. The landscape has changed; the fundamentals have not.

2025

Teaching My Son to Debug

He is ten and wanted to build a game. I sat beside him and watched him struggle with off-by-one errors for a week. It was the hardest and best parenting decision I made this year.

Infrastructure as Autobiography

Your deployment pipeline reveals more about your team than any retrospective. I dissect three real pipelines and what they say about the organizations that built them.

The Quietest API I Ever Built

It processed eleven million requests a day, had four endpoints, and required zero on-call pages in eighteen months. This is its story.

Against “Move Fast and Break Things”

Speed without direction is just thrashing. A case for measured velocity, careful interfaces, and the discipline of saying “not yet.”

Configuration as a First-Class Citizen

Most applications treat configuration as an afterthought — a .env file, some environment variables, maybe a YAML file. Here is a better way.

Saturday Mornings with a Soldering Iron

I have been restoring a 1978 Marantz receiver with my daughter. She is learning about capacitors. I am learning about patience.

Dockerfiles as Documentation

A well-written Dockerfile tells you everything about an application’s runtime dependencies, build process, and operational assumptions. Most are written poorly.

The Virtue of the Monorepo

After years of maintaining dozens of microservice repositories, I moved everything into a single monorepo. The results were immediate and surprising.