You know that guy in every horror movie who hears a noise in the basement and goes to check it out alone, without a flashlight, whistling the whole way down? You might have been him before if you ever just shipped a fix, closed the ticket, and shut the laptop.
The World Economic Forum just put systems thinking as one of the fastest-growing skills through 2030, and almost nobody applying for your job knows what the hell it really means. Which tracks, because AI is now writing the code fast enough that speed stopped being anyone's edge. What's still scarce is the person who checks the basement before the sequel writes itself into your database at 2 a.m.
I got two engineers who've already made that jump to show exactly what separates the guy who dies in scene one from the one who doesn't: Saeed Salehi, who's spent 14 years building software and now leads technical teams at RTL Netherlands, and Vasu Raj Jain, a senior engineer at Amazon Ads who keeps Prime Video's live sports streams from face-planting mid-game.
What we get into:
Why the exact same ticket produces two totally different engineers — and only one of them survives the sequel
The two questions you can start asking on your very next ticket, no course, no permission, no promotion required
How "just add more servers" can turn into a full database outage, and what the fix should've asked first
Why AI writing code faster just moved the bar to judgment, not speed — and judgment doesn't ship in an update
Final girls don't have superpowers. They just ask what's still out there before it gets them. Ask it on your next ticket.
Transcript
