Posts
22
Articles currently hosted on my site and cross-posted to Medium.
Latest
Recent writing with a practical bias.
Start with the latest piece, then browse the rest by topic and depth.
Featured article Guide 7 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.
In series: The santi020k way · Part 11
Filter posts
All posts #typescript 10 #react 8 #nextjs 7 #eslint 5 #developer-experience 4 #frontend 3 #git 3 #vitest 3
Writing Opinion 9 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.
In series: The santi020k way · Part 10
Writing Case Study 8 min read
Why I Moved My ESLint Library to @santi020k/eslint-config-basic
Why I deprecated @santi020k/eslint-config-santi020k in favor of a composable monorepo with clearer packages, better docs, and stronger DX.
In series: ESLint in Practice · Part 3
Writing Opinion 3 min read
Avoid Inverted Conditionals When Clarity Matters
Positive conditionals usually reduce mental load and make branches easier to scan, review, and change.
In series: The santi020k way · Part 9
Writing Guide 4 min read
A Release Process That Reduces Drama
A release process should lower stress, tighten feedback loops, and make production changes easier to trust.
In series: The santi020k way · Part 8
Writing Deep Dive 4 min read
Code Standards That Scale With a Team
The version of coding standards I would actually hand to a growing frontend team today.
In series: The santi020k way · Part 7
Writing Deep Dive 4 min read
Responsive Design Standards That Scale Across Components
Responsive work gets easier when breakpoints and layout decisions are treated like a shared system.
In series: The santi020k way · Part 6
Writing Guide 4 min read
Git Best Practices for Calm Collaboration
Simple commit and pull-request habits that reduce review friction and make collaboration calmer.
In series: The santi020k way · Part 5
Writing Guide 3 min read
Write Better Review Feedback with Conventional Comments
A lightweight review language that makes feedback clearer, kinder, and easier to act on.
In series: The santi020k way · Part 4
The santi020k way Browse the full series
A clearer home for my engineering principles.
A new blog section collecting the principles I keep returning to around ownership, code quality, feedback, responsive thinking, and calmer releases.
This series turns a private set of notes into public writing. The throughline is simple: stronger teams care about the whole system, not just the local task in front of them.
The posts cover ownership, code smells, review language, Git habits, responsive standards, team conventions, release discipline, and small readability choices that compound over time.
11 posts Newly imported
Focus areas
Engineering Culture Code Quality Code Review Delivery Systems
It is the right track if you want the cultural and operational rules behind how I like to build software teams, not only the framework-specific implementation details.
Series Browse all series
Follow related posts in order.
Related posts now live in clearer tracks, so topics like Next.js delivery systems and ESLint tooling feel like connected reading instead of isolated entries.
Active series 7 posts
Building a Production Next.js App
A practical sequence for turning a fresh Next.js codebase into a product teams can lint, test, document, deploy, and secure with confidence.
Next.js Testing CI-CD Architecture
A guided walkthrough from project structure to auth and delivery.
Browse series Active series 3 posts
ESLint in Practice
A focused track on config design, migrations, and the standards work that keeps code reviews sharper without slowing teams down.
ESLint Developer Experience TypeScript
Evergreen tooling notes for teams standardizing JavaScript and TypeScript work.
Browse series Active series 11 posts
The santi020k way
A running set of principles on ownership, review quality, code clarity, responsive thinking, and releases that do not rely on heroics.
Engineering Culture Code Quality Code Review Delivery Systems
Opinionated field notes on how strong software teams stay clear, calm, and accountable.
Browse series Cadence View the full content calendar
A documented monthly publishing rhythm.
One flagship post each month, plus one refresh to an older evergreen article so the archive keeps compounding instead of aging in place. The current roadmap runs from April 2026 through September 2026 so the site keeps growing on a predictable rhythm instead of in bursts.
April 2026 Opinion
AI Coding Is Probabilistic. Your Delivery Process Should Not Be.
Refreshing: Continuous Integration and Deployment for Next.js Projects
May 2026 Guide
Playwright accessibility checks that teams keep running
Refreshing: Testing React Components with Vitest and React Testing Library
June 2026 Opinion
Why developer experience work should be measured like product work
Refreshing: Development Workflow with Husky for Next.js, ESLint, and Vitest Integration