Theo argues that junior-to-senior developers should generally consider management, but his real conclusion is the opposite of the article title: he thinks the skills gained from management—especially communication, goal-setting, and alignment—are broadly valuable, and that the option to become a manager should usually be taken if it genuinely interests you.
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.
This video is a long reaction to an article arguing against becoming an engineering manager. Theo starts by framing software careers as a strange progression where many engineers eventually get pushed out of pure coding into management, often because salary and promotion ceilings rise with leadership responsibility. He agrees with the premise that the industry is changing quickly, especially with AI and agentic tooling, but he disagrees with the article’s final “don’t do it” posture. His core thesis is that management is not just a career ladder choice; it is a skill-building path, and the communication and clarity it forces can make someone better at engineering, leadership, and life more generally. He spends a large portion of the video debating the article’s first major point: moving away from technical work is a bad time right now because the software field is changing too fast. …
Near term, the tactical question is whether the immediate EM offer is worth the title and comp tradeoff versus staying IC; Theo’s bias is to take the role if you genuinely want it. The biggest immediate risk is misreading the role as a pure step up when it may actually reduce autonomy and slow future optionality.
Over the next few months, the path he favors is skill accumulation: become better at communication, alignment, and prompt/goal framing, regardless of ladder. If management does not fit, he expects switching back to IC to remain viable, but the market will reward clearer evidence of scope and communication.
Structurally, he sees the durable edge as transferable communication skill, not any one ladder position. In a world of AI agents and flatter orgs, the people who can define goals precisely and coordinate complex work may end up more valuable than people who only execute tasks.
The skills you develop as an engineering manager — especially communication clarity — greatly benefit you as an engineer and as a practitioner of AI agent development.
Speaker argues that management forces you to become clearer, which helps with AI agents, coding, and all relationships.
Senior engineers should take the management opportunity rather than avoid it, despite prevailing advice to the contrary.
The speaker disagrees with the article's conclusion to wait, arguing management builds universally valuable communication skills that help in a future with more AI agents.
Specifying a goal rather than a task in a prompt dramatically improves AI model performance and alignment with user intent.
Speaker realized after iterating that the only way to get Codex to build its own engine was to explicitly state the goal ('build a chess engine from scratch') rather than implying the goal through the task description.
Unlock the full claims, asset map, scores, related transcripts, follow-up questions, and AI chat — shaped around your portfolio, watchlist, favorite speakers, and risks.
