Reading code to onboard onto a new codebase sounds simple until you’re actually doing it. You start tracing a single user flow, follow a maze of dependency injections, and before you know it, you’ve opened more tabs than lines of code you'll actually end up writing, completely disconnected from the ticket on your board. In my five years as a software engineer, most recently on the Paid Ads team at Wix, I’ve had to do this quite a few times. My default approach was always the

A user opens a support ticket. Their subscription cancellation stopped working. Somewhere inside a system with thousands of services and millions of users, something broke. Before we built Wix Orchestrator, here's what happened next: the ticket joined a queue. Days later, a support engineer picked it up, tried to reproduce the issue, contacted the customer to gather more context, and opened a Jira ticket routed to R&D. We triaged it, prioritized it against everything else on

How do we scale Wix and still keep dev velocity and standards? Tomer Pilossof (Head of DevEx) and Ethan Pogrebizsky (CTO of DevEx)...