Posts
8
Posts connected by this topic in the archive.
Posts
8
Posts connected by this topic in the archive.
Total topics
62
Distinct topics across the full writing archive.
Related topics
Start with the latest post tagged #developer-experience, then browse the rest.
Why I built Astro Doctor: a CLI, ESLint plugin, editor extension, GitHub Action, and agent skill system for catching Astro anti-patterns early.
A practical tour of the shipped @santi020k/eslint-config-basic v2.0 release: ESLint 10, one main install, lazy frameworks, lite mode, monorepos, CLI checks, and AI standards.
In series: ESLint in Practice · Part 5
DX improvements that cannot be measured rarely survive long enough to compound. Treating them like product work changes that.
In series: The santi020k way · Part 12
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
Simple commit and pull-request habits that reduce review friction and make collaboration calmer.
In series: The santi020k way · Part 5