Approach & Mindset
I solve problems like puzzles. Not always linearly, and rarely by following a script. My thinking is flexible, creative, and pattern-driven. Give me the Lego bricks and context, and I’ll build solutions that go beyond the instruction manual.
I enjoy finding unexpected paths, noticing what's not obvious, and building elegant solutions that are clean, robust, performant, and future-ready. While others look for step-by-step guides, I often look for principles and patterns.
Ownership
I do my best work when I can take ownership of a problem from understanding it through to delivering a solution. I enjoy collaborating but I find the greatest satisfaction in building something coherent that can be maintained, improved and trusted over time.
Remote-First, Async-Strong
I work best with space. Space to think, test, write, and iterate. That’s why I favour asynchronous communication over constant check-ins. I’ll always respond thoughtfully and promptly, but I don’t need a daily call to stay aligned.
Agile, But Make It Real
I value Agile when it helps teams deliver, learn and improve. I'm less interested in ceremonies for their own sake.
Too often, teams “flex” the process into something that looks Agile, but really isn't. People work on unsized work or sneak in scope with “I might as well do that while I’m here” logic. That’s how scope creeps, timelines slip and tech debt builds.
Working With Me
- Give me a clear goal and context: I’ll ask questions if needs be, then get moving.
- Async > meetings: I value deep work time. I’ll always respond, but I work best with autonomy.
- Scope control matters: “One quick tweak” or "a quick and dirty addition" is never just that. Let’s be intentional about change.
- I challenge with care: I’ll raise a flag if we’re veering off course and I welcome being challenged, too.
- Users first, not dev-first: A clever solution means nothing if it isn’t usable or scalable. Let's build for users, not for egos.
What I Avoid
- Style over substance Shiny slides, vague logic or solutions that break when the underlying data changes (which it will).
- Hierarchy-driven design: Good ideas should win, not job titles.
- Fake agility: If we don’t size it, track it, or close the loop and therefore learn for next time, we’re not Agile.