Blog series

The santi020k way. A reading track.

A running set of principles on ownership, review quality, code clarity, responsive thinking, and releases that do not rely on heroics.

Browse all series Back to blog

Start to finish
Opinionated field notes on how strong software teams stay clear, calm, and accountable.
14 posts

Posts

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

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.

Part 1Dec 8, 20244 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

Part 2Jan 7, 20254 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

Part 3Mar 29, 20254 min read

Avoid Magic Strings in TypeScript and JavaScript

Replace ad-hoc string literals with clearer domain language, stronger typing, and safer refactors.

typescriptjavascript

Part 4May 17, 20253 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

Part 5Jul 21, 20254 min read

Git Best Practices for Calm Collaboration

Simple commit and pull-request habits that reduce review friction and make collaboration calmer.

gitpull-requests

Part 6Sep 12, 20254 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

Part 7Sep 14, 20254 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

Part 8Oct 5, 20254 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

Part 9Oct 13, 20253 min read

Avoid Inverted Conditionals When Clarity Matters

Positive conditionals usually reduce mental load and make branches easier to scan, review, and change.

readabilityjavascript

Part 10Apr 15, 20269 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.

Part 11Apr 29, 20267 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.

Part 12Jun 12, 20266 min read

Why Developer Experience Work Should Be Measured Like Product Work

Measure developer experience with cycle time, feedback speed, onboarding time, recovery time, and tooling interruptions. Start with a baseline.

developer-experienceengineering-culture

Part 13Sep 11, 20266 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

Part 14Sep 24, 20268 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