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

During 2026, I shipped code that I don't fully understand. It was written in a programming language I'm not even fluent in. A year ago, this would have been a fireable offense. There's no way I would have stood on a stage at a Wix Engineering conference, my employers in the crowd, and said that sentence out loud. Last week, it was just another Tuesday. And here's the part that's been keeping me up at night: I was proud of it. That's a paradox, right? If someone else wrote it,

At Wix, we faced a challenge that will sound familiar to many developers: managing an ever-growing backend codebase spread across 60...