Skin in the Game for Software Teams
Opinión4 min de lectura
Empieza a leerTodas las series
14 artículos conectados
The santi020k way.
A running set of principles on ownership, review quality, code clarity, responsive thinking, and releases that do not rely on heroics.
Opinionated field notes on how strong software teams stay clear, calm, and accountable.
Los 14 capítulosPrinciples 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.
La perspectivaSome 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.
Áreas de enfoque
Explora estos temas en el Blog.
- Engineering Culture
- Code Quality
- Code Review
- Delivery Systems
Artículos en orden de lectura.
Recorre la serie desde los fundamentos hasta la implementación en profundidad.
14 artículos
OpiniónParte 1
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 culture
- Leadership
Leer artículo4 min de lectura
GuíaParte 2
Common Code Pitfalls That Signal Maintenance Risk
The code smells that usually predict rising maintenance cost before a team feels the full pain.
- Code quality
- Maintainability
Leer artículo4 min de lectura
GuíaParte 3
Avoid Magic Strings in TypeScript and JavaScript
Replace ad-hoc string literals with clearer domain language, stronger typing, and safer refactors.
- TypeScript
- JavaScript
Leer artículo4 min de lectura
GuíaParte 4
Write Better Review Feedback with Conventional Comments
A lightweight review language that makes feedback clearer, kinder, and easier to act on.
- Code review
- Engineering culture
Leer artículo3 min de lectura
GuíaParte 5
Git Best Practices for Calm Collaboration
Simple commit and pull-request habits that reduce review friction and make collaboration calmer.
- Git
- Pull requests
Leer artículo4 min de lectura
Análisis a fondoParte 6
Responsive Design Standards That Scale Across Components
Responsive work gets easier when breakpoints and layout decisions are treated like a shared system.
- Responsive design
- Frontend
Leer artículo4 min de lectura
Análisis a fondoParte 7
Code Standards That Scale With a Team
The version of coding standards I would actually hand to a growing frontend team today.
- Engineering standards
- TypeScript
Leer artículo4 min de lectura
GuíaParte 8
A Release Process That Reduces Drama
A release process should lower stress, tighten feedback loops, and make production changes easier to trust.
- Release management
- Git
Leer artículo4 min de lectura
OpiniónParte 9
Avoid Inverted Conditionals When Clarity Matters
Positive conditionals usually reduce mental load and make branches easier to scan, review, and change.
- Readability
- JavaScript
Leer artículo3 min de lectura
OpiniónParte 10
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.
- AI
- ESLint
Leer artículo9 min de lectura
GuíaParte 11
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.
- AI
- Automation
Leer artículo7 min de lectura
OpiniónParte 12
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 experience
- Engineering culture
Leer artículo6 min de lectura
Caso de estudioParte 13
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.
- Architecture
- Documentation
Leer artículo6 min de lectura
Análisis a fondoParte 14
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 experience
- Developer tools
Leer artículo8 min de lectura
Encuentra tu próxima lectura.
Una serie de artículos conectados o una guía para lo que estás creando.