Topic Hub

Software engineering

Production lessons on architecture, debugging, maintainability, deployment workflows, and the tradeoffs that separate toy systems from durable ones.

This is the broadest bucket on the site, but it all comes back to one question: what still makes sense when the code has users, constraints, and consequences?

Start with these articles:

If your problems are mostly about systems getting harder to reason about, this is the lane to stay in.

/ 3 min read

AI-Generated Refactors Are Where False Confidence Gets Expensive

Refactors already carry hidden risk. AI makes it easier to perform larger ones faster, which is exactly why teams need more caution instead of less.

Read article
/ 3 min read

Cross-Functional Ownership Sounds Great Until Nobody Owns Production

Shared responsibility can improve collaboration. It can also become the sentence teams use when accountability is too blurry to survive an incident cleanly.

Read article
/ 3 min read

Your On-Call Rotation Is Telling You the Truth About Your Architecture

The incident pattern your team keeps normalizing is usually a design signal. On-call pain is one of the clearest ways a system reveals where its architecture is actually weak.

Read article
/ 3 min read

Your Test Suite Does Not Need More Tests. It Needs More Trust.

Teams keep adding tests to fix anxiety when the real problem is that nobody believes the suite is telling the truth about production risk.

Read article
/ 3 min read

The Worst Time to Design Permissions Is After You Land an Enterprise Customer

Teams love postponing access-control design until a big customer forces the issue. By then the system already has assumptions baked into it that are painful to unwind.

Read article
/ 3 min read

Retries Are Not Reliability

Repeating a failing action can be useful. It can also multiply load, duplicate side effects, and hide the fact that the system was never designed to fail safely.

Read article