Boring Is Good
I would rather use dependable tools than chase whatever is trending this month.
This is what I actually use day to day to plan, build, ship, and stay sane while doing it.
Last updated: March 2026
I would rather use dependable tools than chase whatever is trending this month.
Small deploys, clear logs, and fast feedback beat big risky releases.
My setup should help me do good work for years, not burn out in one sprint.
I use them for scaffolding, repetitive refactors, and first-pass docs so I can spend more time on architecture and edge cases.
My default editor. I keep it simple and keyboard-first so it stays out of the way.
This is where most of my delivery work happens: git, checks, scripts, and debugging.
My main backend stack for systems where reliability and maintainability matter.
My go-to for building practical interfaces quickly.
Great for automation, integrations, and lightweight services.
I use it in side projects to keep sharpening API and concurrency fundamentals.
My main cloud platform for hosting and operations.
My baseline for repeatable builds and safe deploy workflows.
I use both to keep infrastructure changes repeatable and reviewable.
Monitoring and alerts so I can catch issues before users do.
I split work into small reviewable changes so teammates can reason quickly.
I update runbooks in the same sprint, not weeks later.
I run quick Postman or curl checks before handoff to catch integration issues early.
Quiet, portable, and dependable.
A simple desk setup with fewer distractions and longer focus windows.
Weekend baking is my reset ritual. Slower, hands-on work helps clear technical fatigue.
Short cat breaks between focus blocks help me avoid tunnel vision.
Time outdoors keeps my pace sustainable and keeps work in perspective.



They force micro-breaks that reset my attention between deep work blocks.
It sounds small, but those interruptions lower decision fatigue and improve code review quality over long days.