Theo argues that the path to becoming a software developer has changed: learning is still possible, but getting hired now depends much more on competence and likability than it used to. He says AI, a larger applicant pool, and weaker hiring signal make it harder for junior developers to win jobs, so people should deliberately build skill and surround themselves with stronger developers.
Watch on YouTube ›Get the market thesis, key claims, assets, contradictions, and follow-up questions from any financial video — then unlock a version personalized to your portfolio, watchlist, and favorite speakers.
Theo frames the video as advice for learning and growing as a developer in a market that no longer works like it did when he entered the field. He says his older advice was based on a different era, when there were fewer qualified developers and companies hired under urgency, allowing people with imperfect skills to get jobs if they were likable and roughly good enough. He walks through a conceptual model of developer ability as a distribution, arguing that interview processes are noisy and often only roughly place candidates. He uses his own experience at Twitch as an example: he says he bombed interviews, got a contract because the team liked him and needed help, and was able to learn on the job. He contrasts that with today’s environment, where there are many more applicants, laid-off engineers, and AI-assisted portfolios that make it harder to judge real competence. …
Near term, junior dev hiring looks crowded and noisy, with AI making shallow signal easier to fake and therefore less useful. The immediate tactical edge is to show real competence in interviews and avoid relying on projects or GitHub as your main proof.
Over the next several months, the likely path is continued pressure on entry-level candidates unless companies regain urgency or loosen standards. Candidates who can pair genuine skill with strong interpersonal fit should outcompete those relying on credentials or surface-level portfolio signal.
Structurally, software hiring is shifting toward a regime where real capability and context matter more than résumé proxies. AI may not remove junior opportunities, but it likely makes the profession less forgiving and more selective over time.
The way developers learn, grow, and get hired has changed a lot, so old advice may no longer work well.
Theo says the right way to learn and succeed as a dev has changed significantly and his prior advice is less directly applicable now.
New dev success and learning should be treated as separate questions now, because being good at coding is not the same as getting hired.
He explicitly says learning and finding success are now very different questions.
Hiring decisions are noisy, and interviewers can only roughly place a candidate within a range of ability rather than perfectly rank them.
He describes interviewer disagreement and a range-based model of candidate evaluation.
Unlock the full claims, asset map, scores, related transcripts, follow-up questions, and AI chat — shaped around your portfolio, watchlist, favorite speakers, and risks.
