Workflow
Uses
A practical breakdown of the hardware, software, and rituals behind my day-to-day engineering work.
The core workstation
I prioritize reliability over novelty. Fast boot, stable thermals, and predictable battery behavior matter more than benchmark peaks.
- Laptop: 14-inch class machine with 32GB RAM
- External display: single 4K monitor for focused layout
- Audio: closed-back headphones for deep work
Editor and terminal
Most product work happens in VS Code with a minimal extension set. The terminal is split between quick command execution and long-running service panes.
- Editor: VS Code + strict linting + format on save
- Terminal: WezTerm with project-specific panes
- Shell: Zsh with aliases for repetitive tasks
Design and writing stack
I use lightweight design notes before writing UI code. For writing, I favor short sections and concrete language so documents can convert into implementation quickly.
- Wireframes: low-fidelity notes first
- Writing: markdown with section-first structure
- Knowledge capture: reusable snippets and checklists
Default engineering principles
Tools change, but these defaults stay stable across projects and teams.
- Ship thin slices with production-level quality
- Automate checks early: lint, typecheck, and smoke tests
- Keep dependencies small and documented
- Prefer readability over clever abstraction
