How I Work
Working style, tools, communication preferences, and the systems I use to do good work consistently.
Working Style
How I approach the work itself.
Async-first
Written communication before calls. Structured briefs eliminate ambiguity before decisions are made — no one's time is wasted on a call that could have been a document.
Deep focus mornings
Complex problems and heads-down coding happen in the morning. Collaborative work, reviews, and communication happen in the afternoon.
ADHD-informed
I use time-boxing, visual progress tracking, and explicit acceptance criteria by default. Clear constraints are a feature, not a restriction.
Documentation-heavy
Decisions get written down. Processes get templates. If something is worth doing twice, it gets a system.
Tools Stack
What I reach for when building and operating.
Communication Preferences
How I prefer to work with collaborators and clients.
Written > verbal
Anything requiring a decision gets a written brief first. This creates a record, reduces misalignment, and lets async participants contribute.
Async by default
Calls are reserved for genuinely complex problems where back-and-forth is faster than text. Most things don't need a meeting.
Issues as contracts
Tickets and issues should have explicit scope, acceptance criteria, and a clear definition of done. Ambiguous issues produce ambiguous work.
Feedback via comments
Feedback belongs on the work itself — in a PR, on a document, or in an issue thread. Real-time review sessions create pressure and miss nuance.
ADHD-Informed Approach
Working with my brain, not against it.
Hyperfocus as an asset
When a complex problem lines up with available energy, it gets a genuinely deep solution. I structure work to create the conditions for that to happen.
Structure reduces friction
Checklists, templates, and routines aren't bureaucracy — they're the scaffolding that lets me move fast without dropping things.
Time awareness tools
Visual timers, time-blocking, and explicit deadlines keep me honest. I don't rely on internal clocks — I build external ones.
Systems over memory
I build systems so I don't have to remember things. If it lives in my head, it's a liability. If it lives in a tool, it's reliable.
Sound like a fit?
If this matches how you like to work, we'll probably get along well.