Page 2 of 4
Latest post first, then browse by topic and depth.
How to add accessibility automation to your Playwright suite in a way that is fast enough to stay in the workflow and specific enough to actually catch problems.
In series: Building a Production Next.js App · Part 8
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
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
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
Positive conditionals usually reduce mental load and make branches easier to scan, review, and change.
In series: The santi020k way · Part 9
A release process should lower stress, tighten feedback loops, and make production changes easier to trust.
In series: The santi020k way · Part 8
The version of coding standards I would actually hand to a growing frontend team today.
In series: The santi020k way · Part 7
Responsive work gets easier when breakpoints and layout decisions are treated like a shared system.
In series: The santi020k way · Part 6
Simple commit and pull-request habits that reduce review friction and make collaboration calmer.
In series: The santi020k way · Part 5
