Posts
14
Articles collected into this reading track.
Cadence
Opinionated field notes on how strong software teams stay clear, calm, and accountable.
Publishing rhythm for this series.
Focus areas
4
Recurring themes shaping the articles in this track.
Principles that keep compounding
This series turns a private set of notes into public writing. The common thread is simple: teams get faster when they stop treating quality, communication, and delivery as separate conversations.
Some of these posts are about code. Some are about reviews, releases, and the habits around the code. Together they describe the standards I keep coming back to when I want a team to scale without becoming noisy, fragile, or dependent on heroics.
Focus areas
Engineering CultureCode QualityCode ReviewDelivery Systems
Posts
Articles in this series.
Read these in order if you want the clearest progression from foundations to deeper implementation decisions.
Opinion
Part 14 min read
Skin in the Game for Software Teams
Why strong engineers care about product outcomes, users, and system health instead of stopping at ticket completion.
engineering-cultureleadership
Guide
Part 24 min read
Common Code Pitfalls That Signal Maintenance Risk
The code smells that usually predict rising maintenance cost before a team feels the full pain.
code-qualitymaintainability
Guide
Part 34 min read
Avoid Magic Strings in TypeScript and JavaScript
Replace ad-hoc string literals with clearer domain language, stronger typing, and safer refactors.
typescriptjavascript
Guide
Part 43 min read
Write Better Review Feedback with Conventional Comments
A lightweight review language that makes feedback clearer, kinder, and easier to act on.
code-reviewengineering-culture
Guide
Part 54 min read
Git Best Practices for Calm Collaboration
Simple commit and pull-request habits that reduce review friction and make collaboration calmer.
gitpull-requests
Deep Dive
Part 64 min read
Responsive Design Standards That Scale Across Components
Responsive work gets easier when breakpoints and layout decisions are treated like a shared system.
responsive-designfrontend
Deep Dive
Part 74 min read
Code Standards That Scale With a Team
The version of coding standards I would actually hand to a growing frontend team today.
engineering-standardstypescript
Guide
Part 84 min read
A Release Process That Reduces Drama
A release process should lower stress, tighten feedback loops, and make production changes easier to trust.
release-managementgit
Opinion
Part 93 min read
Avoid Inverted Conditionals When Clarity Matters
Positive conditionals usually reduce mental load and make branches easier to scan, review, and change.
readabilityjavascript
Opinion
Part 109 min read
AI Coding Is Probabilistic. Your Delivery Process Should Not Be.
AI speeds up code changes, but ESLint, tests, snapshots, and end-to-end checks are what keep probabilistic output from turning into production risk.
aieslint
Guide
Part 117 min read
Muted Commands Make AI Automation Faster and Cheaper
AI agents rerun checks constantly. Quiet logs, compact reporters, and parallel verification reduce token waste without lowering the quality bar.
aiautomation
Opinion
Part 126 min read
Why Developer Experience Work Should Be Measured Like Product Work
DX improvements that cannot be measured rarely survive long enough to compound. Treating them like product work changes that.
developer-experienceengineering-culture
Case Study
Part 136 min read
What Changed When I Started Writing Architecture Notes Every Month
A year of monthly architecture notes changed how I review systems, how I catch drift, and how I explain decisions to the people who inherit them.
architecturedocumentation
Deep Dive
Part 148 min read
How I Built the santi020k Developer Tool Ecosystem
How Lumen, ESLint Config Basic, Quality, Astro Doctor, Commitprompt, Dep Beacon, OG, Theme, and Auth form one practical system for my projects.
developer-experiencedeveloper-tools