Overcommitted | Software Engineering and Tech Careers Insights

The crew chat about our experience using AI right now as software engineers (which is subject to change even by the time this episode airs). Including an overview of our current thoughts on the AI landscape, what tools we use for which tasks, and our thoughts on what we are excited about for the future!LinksThe S in MCP Stands for SecurityBook: The Scaling EraOvercommitted on BlueskyHostsOvercommitted.devBethany Janos: https://github.com/bethanyj28Brittany Ellich: https://brittanyellich.comEggyhead: https://github.com/eggyheadJonathan Tamsut: https://jtamsut.substack.com

Join Erika, Bethany, Jonathan, and Brittany for a deep dive into one of every developer's most common challenges: learning a new codebase. Based on Brittany's popular GitHub blog post, this episode shares battle-tested strategies for getting up to speed quickly—whether you're joining a new team, switching projects, or contributing to open source.Working on large-scale systems at GitHub has taught these engineers that you'll never understand everything, and that's okay. The key is knowing where to start and how to build knowledge efficiently while staying productive.Practical strategies discussed:Starting with a single issue to avoid overwhelmCreating personal documentation as you learnUsing pair programming to accelerate onboardingLeveraging GitHub Copilot for code explanation and documentationReading telemetry and Sentry alerts to understand system behaviorUsing debuggers to trace code execution pathsSetting up 1:1s with engineers, PMs, and designers for domain knowledgeFinding good first issues in large codebasesGenerating entity relationship diagrams from database schemasKey mindset shifts:Getting comfortable with not knowing everything at scaleUnderstanding abstraction boundaries through hands-on workDistinguishing between lack of experience vs. understandingRecognizing your contribution's place in the larger systemSpicy hot takes segment: The hosts share their biggest code base pet peeves, including outdated README files that don't work, stale TODO comments from years ago, unhelpful PR templates with required fields, and distributed systems that won't run locally.Whether you're onboarding to a new team, exploring an unfamiliar microservice, or diving into an open source project, this episode offers actionable advice for confident, efficient code base learning.Linkshttps://github.blog/developer-skills/application-development/how-github-engineers-learn-new-codebases/HostsBethany Janos: https://github.com/bethanyj28Brittany Ellich: https://brittanyellich.comEggyhead: https://github.com/eggyheadJonathan Tamsut: https://jtamsut.substack.com/

Join Bethany, Brittany, and Jonathan as they reflect on their first quarter using the 12 Week Year goal-setting framework. This candid retrospective reveals what actually works (and what doesn't) when trying to balance ambitious career goals with the demanding life of a software engineer.Inspired by Brian Moran's "The 12 Week Year" and Ali Abdaal's productivity strategies, the hosts formed an accountability group to track quarterly goals—from newsletter writing and conference talk submissions to fitness and reading habits. Now, three months in, they're sharing their wins, failures, and lessons learned.What you'll learn:How to apply the 12 Week Year methodology to tech career goalsWhy quarterly goal setting works better than annual resolutions for developersCreating accountability groups that actually stickBalancing personal development with demanding engineering rolesHow to reframe "failure" when you don't hit your targetsThe value of setting goals even when you over-commitQuarterly highlights discussed:Publishing The Balanced Engineer newsletter weekly (Brittany's journey)Submitting conference talks to GopherConReading goals (including Gödel, Escher, Bach)Building consistent workout and stretching habitsLearning design fundamentals as a backend engineerWriting technical blog postsBonus segment: The hosts share app ideas they'll never have time to build, including Friend OS (a CRM for personal relationships), a customizable standing desk timer, and alternatives to Facebook Events for casual event planning.Whether you're crushing your goals or struggling to start, this episode offers honest insights into sustainable personal growth for busy engineers.Join Bethany, Brittany, and Jonathan as they reflect on their first quarter using the 12 Week Year goal-setting framework. This candid retrospective reveals what actually works (and what doesn't) when trying to balance ambitious career goals with the demanding life of a software engineer.Inspired by Brian Moran's "The 12 Week Year" and Ali Abdaal's productivity strategies, the hosts formed an accountability group to track quarterly goals—from newsletter writing and conference talk submissions to fitness and reading habits. Now, three months in, they're sharing their wins, failures, and lessons learned.What you'll learn:How to apply the 12 Week Year methodology to tech career goalsWhy quarterly goal setting works better than annual resolutions for developersCreating accountability groups that actually stickBalancing personal development with demanding engineering rolesHow to reframe "failure" when you don't hit your targetsThe value of setting goals even when you over-commitQuarterly highlights discussed:Publishing The Balanced Engineer newsletter weekly (Brittany's journey)Submitting conference talks to GopherConReading goals (including Gödel, Escher, Bach)Building consistent workout and stretching habitsLearning design fundamentals as a backend engineerWriting technical blog postsBonus segment: The hosts share app ideas they'll never have time to build, including Friend OS (a CRM for personal relationships), a customizable standing desk timer, and alternatives to Facebook Events for casual event planning.Whether you're crushing your goals or struggling to start, this episode offers honest insights into sustainable personal growth for busy engineers.Links12 week yearAtomic habitsHabit kitObsidian templateGodel Escher BockThinking in SystemsPartifulHostsBethany Janos: https://github.com/bethanyj28Brittany Ellich: https://brittanyellich.comJonathan Tamsut: https://jtamsut.substack.com

Join GitHub software engineers Jonathan Tamsut, Brittany Ellich, Erika Egemeyer, and Bethany Janos as they break down one of tech's most common yet rarely discussed challenges: imposter syndrome.In this inaugural episode, four career-changers share their personal experiences with feeling like frauds despite proven success. Drawing from the foundational 1978 research by Pauline Clance and Suzanne Imes, the hosts explore why so many engineers—regardless of background—struggle with self-doubt and fear of being "exposed."Topics covered:The myth of the "basement programmer" and how industry stereotypes fuel imposter syndromeWhy career changers (from chemistry, biomedical engineering, and other fields) often feel they don't belongThe problematic "10x developer" narrative and why team collaboration matters moreHow to measure your own success beyond technical prowessCreating psychologically safe team environments where asking for help is normalizedPractical strategies for combating imposter syndrome and building confidenceThe importance of inclusive language and accessible codeWhether you're a seasoned engineer or just starting your career, this honest conversation offers validation and actionable insights for anyone who's ever wondered if they're "technical enough" to be in tech.Linkshttps://howwefeel.org/https://www.everywoman.com/my-development/quiz-there-are-5-kinds-imposter-syndrome-which-one-yours/ HostsBethany Janos: https://github.com/bethanyj28Brittany Ellich: https://brittanyellich.com/Eggyhead: https://github.com/eggyheadJonathan Tamsut: https://jtamsut.substack.com/