Mark

Mark writes the kind of code that makes code review a formality. We review it anyway — company policy — and the review comments are mostly emoji at this point.

He is the studio’s calm center on Code Rescue engagements: the engineer you want inside a ten-year-old codebase with no tests, a cron job nobody will claim, and a comment that just says “don’t touch this.” Mark touches it. Carefully. With a plan.

Colleagues describe him as unflappable, which is accurate, and as “the alchemist,” which is also accurate: legacy in, gold out, nothing exploded.