Jimmy Jansen

Currently

Working on a video platform that goes from idle to 50k+ requests in a second, and exploring options for an internal developer platform we're shaping in-house.

• Simplicity Is an Architectural Decision

  Simplicity is not the absence of design. It is the result of knowing which complexity has earned its place, where it belongs, and which imaginary futures are not worth paying for.

• A Pragmatic Testing Strategy

  Years of debates with developers, POs, management, and leadership have shaped my perspective. This is what I've learned about pragmatic testing in the real world, the patterns that work, the fights worth having, and the compromises that matter.

• Platform consolidation

  Three product platforms merging into one. Three data models that had to keep talking to each other while old and new customers ran side by side. Twelve teams, five months, and architecture decisions that couldn't break any account, especially the big ones sales was watching.

• Technical strategy across teams

  Most teams now ship with ADRs and RFCs. Supporting twelve team leads on the technical feasibility of their quarterly plans. Thirty-plus consulting engagements before that, brought in to make the architectural calls on builds under pressure, with teams set up to keep going after I rolled off.

• Building what customers use

  Customer-facing work across video platforms at scale, consumer mobile apps, and consultancy engagements spanning startups to enterprises.