Archivo del blog
Artículos anteriores de la página 3 de 4, de los más recientes a los más antiguos.
12 artículosEn esta página
Artículos 25–36 de 47
Explorar por tema
Los 112 temasRun tested Playwright and axe examples for page scans, dialog focus, and skip links, then use a keyboard checklist to review what automation cannot prove.
AI agents rerun checks constantly. Quiet logs, compact reporters, and parallel verification reduce token waste without lowering the quality bar.
AI speeds up code changes, but ESLint, tests, snapshots, and end-to-end checks are what keep probabilistic output from turning into production risk.
Why I deprecated @santi020k/eslint-config-santi020k in favor of a composable monorepo with clearer packages, better docs, and stronger DX.
Positive conditionals usually reduce mental load and make branches easier to scan, review, and change.
A release process should lower stress, tighten feedback loops, and make production changes easier to trust.
The version of coding standards I would actually hand to a growing frontend team today.
Responsive work gets easier when breakpoints and layout decisions are treated like a shared system.
Simple commit and pull-request habits that reduce review friction and make collaboration calmer.
A lightweight review language that makes feedback clearer, kinder, and easier to act on.
Replace ad-hoc string literals with clearer domain language, stronger typing, and safer refactors.
The code smells that usually predict rising maintenance cost before a team feels the full pain.
