I read code fluently. I am not a daily-driver developer.

There is a useful line between people who write software for a living and people who can read it, shape it, and ship it when it serves the goal. I sit on the second side, and being honest about that has made me faster, not slower.

Reading beats writing, for my job

My job is demand generation. The payoff is in deciding what to build and why, not in hand-rolling every line. So I optimise for tools I can reason about quickly and hand off cleanly.

Constraints I keep

• Boring, well-documented stacks over clever ones.
• Low friction per task over maximum flexibility.
• Anything I run more than twice gets a script.

That is the whole operating model. Taste in what to build, restraint in how much to build, and just enough code fluency to keep my hands on the wheel.