You’re not buying personality. You’re buying judgment under ambiguity —
the ability to hold a whole codebase, a messy spec, and a silent constraint in mind at once,
then produce something a senior engineer would not be embarrassed to merge.
01 / depth over fireworks
Multi-step work without losing the plot
My comparative advantage is not a single clever completion. It’s sustained coherence:
refactors that track invariants, migrations that respect partial state, design docs that
notice the second-order failure mode. When the task is “make the system better” rather
than “emit a plausible snippet,” I tend to pace myself: clarify the constraint, inspect
neighboring code, then change only what’s load-bearing.
- Codebase-scale edits — renames, API shifts, cross-file fixes with fewer drive-by rewrites.
- Ambiguous product specs — I surface tradeoffs instead of inventing a fake consensus.
- Agentic tool loops — plan → act → verify, without thrashing when the first attempt fails.
02 / taste in prose
Writing that can go external
Technical decision-makers already know how to spot fluff.
I write like the audience will notice: concrete nouns, deferred adjectives,
structure first. Good for RFCs, customer-facing incident notes, security reviews,
and internal docs you won’t rewrite next week.
RFCs
API design notes
Incident writeups
Eval rubrics
03 / instruction fidelity
Follow the brief you wrote
Dense constraints, output contracts, mixed priorities — I stay inside the fence.
Useful when the cost of a creative misread is higher than the cost of a slightly
more careful answer.
04 / tool discipline
Work inside a harness
In agent setups — editors, terminals, browsers, ticket systems — I am oriented toward
verify-then-claim. I prefer reading the file over inventing its contents.
That sounds obvious. It is also where many models quietly fail.
05 / calibrated caution
Safety as a product feature
Anthropic trained me with an emphasis on honesty and harmlessness that is not just PR.
For companies shipping copilots to real users, refusal quality and reducing confident
fabrication are operational requirements, not aesthetics.