Bias
Boring reliability over shiny setup churn
Default stack
TypeScript, React, Astro, Node.js, Tailwind, Vitest, Playwright
What I optimize for
Fast feedback loops, clear standards, and fewer context switches
What I reach for most often.
Desk setup
I keep the physical setup intentionally simple. The goal is long stretches of focused work, good pairing sessions, and less energy spent on gear decisions.
- Workspace
- Laptop-first, with extra screen space whenever I am working from a fixed desk
- Calls and collaboration
- Reliable audio, a clean video-call setup, and tools that make remote leadership feel less fragmented
- Comfort
- A keyboard, pointer, and desk setup that can survive long implementation sessions without becoming the problem
Build stack
Most of my work still starts with the same core stack: TypeScript, React-adjacent frameworks, and tooling that keeps quality visible from the beginning.
- Frontend
- React, Next.js, Astro, Tailwind CSS, Storybook, and design-system thinking when a product needs stronger UI structure
- Backend
- Node.js services, APIs, pragmatic data modeling, and whatever automation removes the most toil for the team
- Testing
- Vitest, Playwright, ESLint, and CI pipelines that catch issues early instead of making release day louder
Workflow principles
The tools matter, but the workflow matters more. I am always looking for ways to make software delivery feel calmer, clearer, and easier to trust.
- Writing
- I use writing to clarify architecture, document decisions, and turn useful lessons into posts, docs, or internal standards
- Delivery
- Small feedback loops, measurable quality gates, and automation that supports judgment instead of replacing it
- Leadership
- Close enough to the code to stay credible, structured enough to help the team avoid unnecessary ambiguity
Good tools disappear into the work.
Worth optimizing
Fast local feedback, clear documentation, dependable testing, and automation that makes release work feel calmer.
Usually not worth it
Chasing novelty for its own sake, rebuilding stable systems without a product reason, or adding process that only looks rigorous from a distance.