Realistic advice about software dev right now
TL;DR
Breaking into dev is no longer the same game Theo played in 2016 — he says he got paid $125k at Twitch to basically learn on the job, a path made possible by hiring urgency, weak evaluation, and team fit that’s much rarer now.
The hiring market shifted from 'can we fill this seat?' to 'why pick you over 1,000 applicants?' — Theo frames hiring as urgency, likability, and competence, and argues juniors can’t rely on low competence being masked by charm the way some devs once could.
Your fastest path to getting better is being around people who make you feel slightly outclassed — his big test is whether you regularly spend time with better devs in real life or online, because without that measuring stick you get trapped in Dunning-Kruger or imposter syndrome.
Community is not a side quest; it’s how competence and opportunity compound — Theo’s examples include Gabriel going from $11/hour to a full-time role and Basim getting hired by Assistant UI after Theo found his two-star React Shiki library and reached out.
Ask AI for hints and reasoning, not finished code — his advice is to ask 'why,' 'how should I approach this,' or 'give me one small hint,' because AI helps when it unblocks deeper learning and hurts when it prevents depth.
The most underrated career move is asking 'who built this?' instead of only 'how does this work?' — Theo says he spends more time on GitHub profiles than repos, and that sincere 2-3 sentence messages to small open-source maintainers can build real relationships in an AI-slop world.
The Breakdown
Theo opens with the hard truth: his old advice aged out
Theo starts by admitting this is much harder to answer than it used to be. The path he took into software eight years ago helped thousands of people, but he’s blunt that if he were 21 and graduating today, he’s not sure he would’ve made it the same way.
Why 'average dev' matters more than people want to admit
He builds a rough bell-curve mental model and says many devs wildly misjudge what average actually is because they only surround themselves with smart people. In classic Theo fashion, he says he knows people making $350k who can’t figure out SSH, using that to explain why bad interview systems still used to let below-average developers through.
The Twitch story: how Theo got hired before he was ready
His own first big break at Twitch is the centerpiece: he bombed the C++ interview so badly they swapped in a front-end interviewer, then he bombed that too. He still got in on a three-month contract because people liked him, the team urgently needed media engineers for things like Bob Ross and Power Rangers streams, and there just weren’t better options fast enough.
The old loophole is closing fast
From there, he sharpens the point: hiring used to be a mix of urgency, likability, and competence, and you could get hired without fully having the third one. Now, with laid-off experienced candidates and AI making GitHub portfolios and polished side projects easier to fake, appearing competent is easier while actually standing out is harder.
The loneliness test for developers
Theo then pivots into one of the video’s most human sections: he asks chat whether they regularly spend time with better devs in real life, and tons of people say no. His takeaway is that a lot of ambitious devs aren’t lazy, they’re lonely — they’re hanging around streams, Discords, and niche communities at 3 a.m. because it feels better than being the only person in their town or class who cares.
Why likability and competence are secretly connected
That loneliness isn’t just emotional; it’s educational. Theo argues you need capable people around you to calibrate your skill, otherwise you either think you’re amazing too early or think you’re terrible forever, and he uses his own YouTube arc — early hits, overconfidence, then a bunch of flops — as a clean Dunning-Kruger example.
Use AI like a tutor, not a ghostwriter
When he finally gets practical, his AI advice is precise: don’t ask it to do the work, ask it how to think. Better prompts are things like 'why doesn’t my solution work?' or 'give me one small hint,' because AI is magical when it helps you go deeper and dangerous when it keeps you shallow.
The real career hack: follow the people behind the code
Theo says one of his biggest advantages has been caring about who made something, not just how it works. He tells two memorable stories: first, how genuine engagement in communities helped people like Gabriel level up; second, how a cold LinkedIn message to Basim — creator of a two-star syntax-highlighting package — led to Basim getting hired by Assistant UI after one interview.
In an AI-slop world, the human touch wins
He closes by saying the best thing new devs can do is follow what genuinely excites them, thank the people building things they rely on, and become someone others remember as curious and generous. The note he ends on is optimistic but realistic: things are harder, but if you care enough to sit through a 54-minute video like this, you probably won’t stay in the bottom half for long.