I'm a senior staff engineer at Sleuth, a SaaS observability platform (the first engineer they hired, de-facto architect), and the person who just gave this talk.
Almost two decades of building software.
Multi-tenant architecture. Circuit breakers guarding 2-3 million third-party API calls a day across about 40 external APIs. Real-time anomaly detection for hundreds of clients.
Python Go Django Celery PostgreSQL Redis RabbitMQ Elasticsearch LLM agents Conference speaking
LinkedIn is the fastest way to reach me.
What makes us really calm when deploying code to production? A green test suite with 100% test coverage. But then we merge, deploy, go to lunch… and somewhere out there a user does something so creative that production goes down anyway. There’s no amount of tests that makes the bugs go away. We wish test coverage was a magic number, just like we want to believe in the power of other metrics (LOC, story points, DORA, …). This talk grapples with two questions: what our tests actually catch, and why we keep reaching for these numbers.
None yet, I haven't written this one up. Accept me at your conference and I'll finally have the time to build it.