Selected case studies showcasing technical depth and impact
How do you scale real-time sports data collection without sacrificing correctness? Started with an Electron app (XState state machines, 30+ contextual keyboard shortcuts) that reduced 16 sequential hours to 4 concurrent collectors. Then built backend DSLs so product managers could define sports rules as configuration—new sports became data, not code. But architecture alone isn't enough: learning to build team ownership took until year three, and geo-political constraints meant the final piece—customer-facing DSLs—never shipped. Lessons: Architectural separation eliminates false trade-offs. Team building shapes what's sustainable. Context determines what works.
How do 20 teams collaborate on wise.com without friction or incorrectness? Building editorial infrastructure that handles global→local fintech complexity—regulations differ by market, offerings vary by country, cultural nuances matter. The challenge is architectural: coherence at scale while preserving developer experience. Still exploring what content collaboration looks like at 16M+ customer scale.