Overcommitted | Software Engineering and Tech Careers Insights

SummaryIn this episode, Erika talks with Salma Alam-Naylor about software engineering craft, programming best practices, and why the long game beats shortcuts. As AI coding tools proliferate and everyone chases speed, Salma digs into deliberate practice, sustainable career strategies, and building genuine expertise that compounds over time. Perfect for engineers feeling burnout from the hype cycle.LinksSalma’s website: https://whitep4nth3r.com/2021 Jamstack Jammies (Community Creator Award) https://2021.jamstackconf.com/jammies/Fat bear week website: https://explore.org/fat-bear-weekHell.com wikipedia: https://en.wikipedia.org/wiki/Hell.comHostsOvercommitted: https://overcommitted.devErika (Eggyhead): https://github.com/eggyhead

Tech careers don't need to mean grinding LeetCode. In episode 57, John Crickett — 30+ year engineer, Coding Challenges creator (90K+ subscribers) — makes the case that programmer productivity skyrockets when you build real tools instead. We dig into why your own Redis, Git, or shell beats practice problems, how Coding Challenges went from $17 domain to viral sensation (1,500 signups in one weekend), and what it means to level up through systems programming.LinksCoding Challenges (Newsletter): https://codingchallenges.substack.com/Coding Challenges Website: https://codingchallenges.fyiFrom The Challenges - Git: https://codingchallenges.substack.com/p/from-the-challenges-gitWill AI Kill Coding?: https://codingchallenges.substack.com/p/will-ai-kill-codingUsing AI To Solve A Coding Challenge: https://codingchallenges.substack.com/p/using-ai-to-solve-a-coding-challengeTech Lead Journal #178 — John Crickett: https://techleadjournal.dev/episodes/178/Confessions of a Data Guy — What Makes Great Engineers: https://www.confessionsofadataguy.com/decades-in-software-engineering-what-actually-makes-great-engineers-john-crickett/Coding Chats Podcast: https://open.spotify.com/show/59GU7gzyK2RdIDVkhNS2ntJohn Crickett on GitHub: https://github.com/johncrickettJohn Crickett on LinkedIn: https://uk.linkedin.com/in/johncrickettJohn Crickett on Bluesky: https://bsky.app/profile/johncrickett.bsky.socialJohn Crickett on X: https://x.com/johncrickettHostsOvercommitted: https://overcommitted.devBethany: https://trustyduck.devBrittany Ellich: ⁠https://brittanyellich.com ⁠Erika: ⁠https://github.com/eggyhead

SummaryCareer growth through mentorship and work-life balance with Dave Schwantes, Senior Software Engineer at GitHub. Brittany and Dave explore why running toward meaningful work beats running from burnout, how mentorship became his primary form of engineering leverage, and what career happiness actually looks like across different life stages. From Instacart and Couchsurfing to building in-house bootcamps, Dave shares how sustainable engineering culture beats individual productivity hacks—and his take on how AI tools reshape what engineers really need to master.LinksDave's personal site: https://dinosaurseateverybody.comDon't Break Prod (bite-sized career advice): https://dontbreakprod.comGrave Danger (Dave's spooky ska band) on Bandcamp: https://gravedangerskath.bandcamp.comDave on Bluesky: https://bsky.app/profile/dorkrawk.bsky.socialDave on LinkedIn: https://www.linkedin.com/in/davidschwantesDave on GitHub: https://github.com/dorkrawkWeb Dev Challenge Episode: https://www.youtube.com/watch?v=X2sEoZG8EIwThe Engineer Manager Pendulum article: https://charity.wtf/2017/05/11/the-engineer-manager-pendulum/HostOvercommitted: https://overcommitted.devBrittany Ellich: https://brittanyellich.com

SummarySabrina Goldfarb rejected the tech career playbook. No CS degree, bootcamp instead, teaching before big platforms. Now an engineer on GitHub's Copilot team and instructor at Frontend Masters, she shares how methodical planning, patience, and trust in the process led to career growth most thought impossible. If you're considering a non-traditional path in software engineering, this episode proves there's more than one way to build a meaningful tech career.LinksFrontend Masters: Practical Prompt Engineering: https://frontendmasters.com/courses/prompt-engineering/Sabrina Goldfarb on LinkedIn: https://linkedin.com/in/sabrinagoldfarbHostsOvercommitted: https://overcommitted.devBethany Janos: https://github.com/bethanyj28Erika (Eggyhead): https://github.com/eggyhead

SummaryIn this episode of the Overcommitted Podcast, hosts Bethany and Erika sit down with Warren Parad, CTO and co-founder of Authress, a user authorization API built for reliability. Warren shares how his team stayed fully operational during the massive AWS US-East-1 outage in October 2025 using DNS failover and multi-region strategies, and what the delayed alert logs taught them about timestamp trust. The conversation kicks off with a candid discussion on AI agents and critical thinking, whether managing multiple coding agents is really multitasking or just micromanagement, and what the trade-offs mean for early-career engineers. Warren traces his reliability-first mindset back to his roots in electrical engineering and healthcare IT, where late-night on-call pages through Citrix proxies and hospital billing systems shaped how he thinks about uptime today. The group also explores what it really takes to build a Five Nines organization and how hiring practices need to match the reliability culture you want. The episode wraps up with a round of Never Have I Ever: SRE Edition, featuring Friday deploys gone wrong, blaming DNS, and discovering outages from customer tweets.LinksAuthress, Warren's company, user authorization API for software makers. The product he's building and wants to plug.Adventures in DevOps Podcast, Warren's podcast, co-hosted with Will Button. 300+ episodes on DevOps, engineering leadership, and cloud architecture.How When AWS Was Down, We Were Not, Authress's blog post detailing their resilience strategy during the October 2025 AWS outage. Referenced in Theme 1 questions.So You Want to Build Your Own Authorization?, Warren's article on why authorization complexity creeps up on teams. Referenced in Theme 2 questions.An Interview With Warren Parad, CIAM Weekly, March 2025 interview covering Warren's views on CIAM, FedCM, and the future of authentication.FedCM, Browser Native Auth (Adventures in DevOps Episode), Adventures in DevOps episode diving into FedCM and why authentication should move from user-land to kernel-land.Warren Parad on LinkedIn, Warren's LinkedIn profile.Warren Parad on Bluesky, Warren's Bluesky profile.Warren Parad on GitHub, Warren's GitHub profile, includes Authress repos, OpenAPI Explorer, and other open-source work.Authress Knowledge Base, Technical articles from the Authress team on auth, security, and infrastructure.Warren Parad, Personal Site, Warren's personal website.HostsOvercommittedBethany JanosErika (Eggyhead)

SummaryIn this episode of Overcommitted, Satish Saley, a senior software engineer with extensive experience on DoorDash's search platform team, discusses scaling search systems at a hyper-growth company. This conversation dives deep into software engineering challenges and software development strategies that impact programmer productivity and career growth. Satish details two major engineering transformations: rebuilding the search indexing pipeline with Kafka, Flink, and Elasticsearch, and later replacing Elasticsearch with a custom search engine based on Apache Lucene, which significantly improved performance and reduced costs.The episode also explores the complexities of migrating off monoliths, securing leadership buy-in for technical rebuilds, and why respecting legacy systems is crucial in engineering culture. Additionally, the hosts share personal stories of database pivots and conclude with a confessional segment on technical decisions that didn't age well. This episode is packed with insights for software engineers and tech professionals interested in the intersection of technology, scaling, and work life balance.LinksSatish Saley on LinkedIn: https://www.linkedin.com/in/satish-saley-65527525/ Conway's Law: https://en.wikipedia.org/wiki/Conway%27s_law Build Faster Indexing with Apache Kafka and Elasticsearch: https://careersatdoordash.com/blog/open-source-search-indexing/ Introducing DoorDash's In-House Search Engine: https://doordash.engineering/2024/02/27/introducing-doordashs-in-house-search-engine/HostsOvercommitted: https://overcommitted.devBethany Janos: https://github.com/bethanyj28Brittany Ellich: https://brittanyellich.com

SummaryIn this special one-year anniversary episode of Overcommitted, Brittany, Erika, and Bethany reflect on their journey from a small accountability group to a thriving weekly podcast and community of over 160 software engineers. They discuss their experiences within the software development lifecycle, the challenges of maintaining programmer productivity, and the evolution of their engineering culture. Listeners will hear candid stories about mastering interview skills, handling the complexities of production admin, and navigating promotional efforts. The episode also highlights the podcast's unexpected role as a valuable networking tool for remote workers in tech careers. Looking ahead, the hosts share exciting plans including new panel-format episodes, community events, and automation initiatives. Closing with affectionate roasts in their first-ever Overcommitted Superlatives, this episode offers both insight and entertainment for anyone passionate about software projects and sustainable work-life balance in tech.LinksEpisode 1 - Imposter Syndrome: https://overcommitted.dev/imposter-syndrome-in-software-engineering/Overcommitted Discord Server: https://discord.gg/d9gZyYuqKdComputer systems: A programmer's perspective: https://www.amazon.com/Computer-Systems-Programmers-Perspective-3rd/dp/013409266XHostsOvercommitted: https://overcommitted.devBethany Janos: https://github.com/bethanyj28Brittany Ellich: https://brittanyellich.comErika Eggyhead: https://github.com/eggyhead

SummaryIn this episode, we dive deep into software development education and programmer productivity with Craig Dennis, developer educator at Cloudflare and creator of AI Avenue. Craig shares his unique journey through tech careers, from early challenges to leading AI education initiatives that empower software engineers to build confidently using AI tools. He champions the philosophy of AI as a power up, not autopilot, encouraging software developers at all levels to embrace AI to enhance their programming skills and accelerate software projects.We explore Craig's insights from interviewing tech companies like ElevenLabs and HeyGen, tackling skepticism around AI in engineering culture, and highlighting powerful AI capabilities such as structured outputs. Craig also reflects on how global reach and innovative teaching methods are shaping the future of software engineering education, inspiring listeners to move beyond theory and start building with AI today.Join us for this insightful conversation on AI's role in software engineering, career growth, and improving work-life balance in tech through smarter development practices.LinksAI Avenue official website: https://aiavenue.show/AI Avenue YouTube playlist (full season): https://www.youtube.com/playlist?list=PLI6HzeeCy4S-XL166XESd9eAV87beBiWHCraig's GitHub: https://github.com/craigsdennisCraig on LinkedIn: https://www.linkedin.com/in/craigsdennis/Cloudflare Developer Week 2025 hub: https://www.cloudflare.com/developer-week/Cloudflare Workers AI documentation: https://developers.cloudflare.com/workers-ai/Model Context Protocol (MCP) on Cloudflare: https://developers.cloudflare.com/agents/model-context-protocol/Build and deploy Remote MCP servers blog post: https://blog.cloudflare.com/remote-model-context-protocol-servers-mcp/HostsOvercommitted: https://overcommitted.devBethany Janos: https://github.com/bethanyj28Brittany Ellich: https://brittanyellich.com

SummaryThis week on Overcommitted, Erika and Brittany welcome Idan Gazit, head of GitHub Next — a senior-heavy innovation team making strategic "long bets" on the future of software engineering and software projects. Idan shares insights into running a cutting-edge team within a large company and how GitHub Next fosters programmer productivity through self-assembling squads, weekly demo days, and discovery seasons. They discuss the pressure and excitement behind delivering revolutionary tools like Copilot.LinksIdan's Website: https://gazit.meGitHub Next Website: https://githubnext.com/HostsOvercommitted: https://overcommitted.devBrittany Ellich: https://brittanyellich.comErika Eggemeyer (Eggyhead): https://github.com/eggyhead

SummaryIn this special in-person episode recorded at the GitHub office, Brittany and Bethany dive into the evolving role of AI agents in software development and programming as of early 2026. They discuss the impact of AI tools like Copilot and Claude Code on programmer productivity and software engineering workflows. The hosts explore practical applications of coding agents, including custom agents and repository instructions, and highlight how asynchronous versus synchronous tooling is reshaping engineering culture. They also share wishes for future AI agents, such as smarter calendar integration and lore-dump assistants, illustrating the expanding possibilities of AI in tech careers. Further, the episode touches on how the developer role intersects with product management amidst easier feature building and complex decision-making. Lastly, Brittany and Bethany forecast advances in AI, including coaching agents to support career growth, tools to balance work life for working parents, and deeper integration of automation to enhance software development and daily productivity.LinksZapier: https://zapier.com/Andrej Karpathy tweet: https://x.com/karpathy/status/2015883857489522876?s=20Vibe Coding by Gene Kim and Steve Yegge: https://www.simonandschuster.com/books/Vibe-Coding/Gene-Kim/9781966280026 The Pragmatic Summit: https://www.pragmaticsummit.com/HostsOvercommitted: https://overcommitted.devBethany Janos: https://github.com/bethanyj28Brittany Ellich: https://brittanyellich.com

SummarySean Goedecke, a staff engineer on GitHub's Copilot team and a prominent voice in software development, shares his unique frameworks for software engineering and improving programmer productivity. In this episode, discover how understanding the distinction between "pure" and "impure" engineering can impact software projects and career growth in tech. Sean breaks down the idea of "legible" vs. "illegible" work, challenges conventional approaches centered around Jira ticket queues, and discusses the evolving role of AI in software engineering. This conversation also touches on the dynamics of engineering culture and how ambitious engineers can thrive beyond typical performance metrics. Plus, Sean responds to some of his most compelling Hacker News comments live on the show, providing fresh insights into balancing productivity with impactful work.LinksSean’s website: seangoedecke.com Blog post: Pure and impure software engineering: https://www.seangoedecke.com/pure-and-impure-engineering/ Blog post: The good times in tech are over: https://www.seangoedecke.com/good-times-are-over/ Blog post: 2025 was an excellent year for this blog: https://www.seangoedecke.com/2025-wrapup/ Seeing like a state book: https://www.goodreads.com/book/show/20186.Seeing_Like_a_State HostsOvercommitted: https://overcommitted.devBethany Janos: https://github.com/bethanyj28Brittany Ellich: https://brittanyellich.comErika Eggemeyer (Eggyhead): https://github.com/eggyhead

What do composing music and fixing bugs have in common? More than you'd think.In this episode of Overcommitted, hosts Erika and Bethany sit down with Marco Herrera Rendon, Senior Engineer at Comcast specializing in Rust development who, not long ago, was applying to master's programs in film composition.Marco shares how his background as a music composition student shapes the way he writes code today: the attention to detail that comes from handing parts to live players (not unlike submitting a PR), and the surprising overlap between navigating from theme A to theme B in a score and tracking down a bug in a codebase. He also digs into why he fell in love with Rust after years of frustration with C++, what he wishes he'd learned first, and his philosophy for picking up new skills: start with 10% comprehension, build a mental model, and embrace not understanding everything at once.In this episode:1. How a composition degree became an unexpected foundation for software engineering2. Rust vs. C++: what finally clicked, and why the borrow checker is a feature not a bug3. The Hector model design pattern and the power of Rust macros4. Learning on the job without shame and why being the least experienced person in the room can be freeing5. Async Rust: the beast within the beast6. What our college selves would think about our careers todayWhether you came to tech through a traditional path or a wildly unconventional one, this conversation is a reminder that the skills you carry from your past life don't disappear, they just find new ways to show up.Links: - Marco's Github: https://github.com/mherrerarendonHosts:- Overcommitted: https://overcommitted.dev- Bethany Janos: https://github.com/bethanyj28- Brittany Ellich: https://brittanyellich.com- Erika Eggemeyer: https://github.com/eggyhead

Summary:In this episode of the Overcommitted Podcast, host Bethany and co-host Brittany Ellich dive into software engineering education with Sam Rose, a developer educator at Ngrok. Sam shares his journey from software engineering to education, emphasizing his innovative approach to improving programmer productivity through visual interactive essays that simplify complex technical concepts like large language models (LLMs). He also discusses his work on prompt caching, aiming to enhance software projects by making technical knowledge more accessible to engineers and practitioners.The conversation explores Sam's unique teaching methods, focusing on visualization and interaction as key tools in software development and career growth within tech careers. Sam reflects on his transition from an engineering role to an educator, sharing insights into the challenges of this career shift, the importance of feedback, and how his personal experiences influence his work. The episode concludes with a playful segment inspired by Sam's educational approach, highlighting the integration of engineering culture with interactive learning.Tune in for an engaging discussion that blends software engineering, education, and work-life balance, offering valuable insights for anyone interested in advancing their tech career and embracing innovative learning strategies.Takeaways:"If you truly understand something and you tinker with it, the mental model you end up with should be reasonably accurate.""Don't say 25 words if you can do it in 15.""Teaching has always felt very challenging in a really privileged way."Links:Prompt caching article: https://ngrok.com/blog/prompt-caching/Bartosz Ciechanowski: https://ciechanow.ski/Load balancing article: https://samwho.dev/load-balancing/Autism diagnosis article: https://samwho.dev/blog/getting-an-autism-diagnosis/Having a baby article: https://samwho.dev/blog/having-a-baby/Write that blog article: https://writethatblog.substack.com/p/sam-rose-on-technical-blogging)The square hole girl video: https://www.youtube.com/watch?v=cUbIkNUFs-4Hosts:Overcommitted: https://overcommitted.devBethany Janos: https://github.com/bethanyj28Brittany Ellich: https://brittanyellich.com

SummaryIn this episode of the Overcommitted Podcast, hosts Brittany, Bethany, and Erika dive deep into the realities of software development with guest Robby Russell. They explore the critical challenges of maintaining legacy code and managing technical debt, emphasizing the impact on programmer productivity and long-term sustainability of software projects. Robby shares his extensive experience, including his journey creating Oh My ZSH, highlighting the importance of documentation, testing, and fostering a collaborative engineering culture. The discussion also covers balancing personal and professional commitments, an essential aspect of career growth in tech. Listeners will gain practical insights into navigating software engineering challenges while sustaining work-life balance. The episode wraps up with a fun segment on current tech obsessions from all participants.LinksPlanet Argon: https://www.planetargon.com/ Oh My Zsh: https://ohmyz.sh/ Maintainable Podcast: https://maintainable.fm/On Rails Podcast: https://onrails.buzzsprout.com/ Robby’s Blog: https://robbyonrails.com/ Robby’s Band: https://mightymissoula.com/ Commit Goods Store: commitgoods.comd’Oh My Zsh: https://medium.com/free-code-camp/d-oh-my-zsh-af99ca54212c Stop Pretending You’re the Last Developer: https://robbyonrails.com/articles/2025/07/16/stop-pretending-youre-the-last-developer/ Internal Tooling Maturity Ladder: https://robbyonrails.com/articles/2025/08/13/internal-tooling-maturity-ladder/Diataxis: https://diataxis.fr/HostsOvercommitted: https://overcommitted.devBethany Janos: https://github.com/bethanyj28Brittany Ellich: https://brittanyellich.comErika Eggemeyer: https://github.com/eggyhead

SummaryIn this insightful episode of the Overcommitted Podcast, hosts Erika, Bethany, and Brittany tackle the critical issue of burnout in software projects and software engineering, especially amid the surge of AI advancements and remote work. They dive into how the evolving programming landscape affects programmer productivity and well-being, highlighting alarming statistics that show 66% of tech workers struggling with burnout symptoms.The conversation sheds light on the balance required between ambitious career growth in tech careers and maintaining work life balance through clear communication and strong boundaries. They discuss how AI influences software development and collaboration while emphasizing the importance of psychological safety within engineering culture to prevent burnout.Listeners will gain valuable insights into managing the pressures of tech work, recognizing when to push back against unrealistic expectations, and sustaining passion in programming careers. The episode closes with a fun segment featuring bold predictions about the future of software engineering, reflecting the hosts' camaraderie and forward-thinking outlook.Takeaways66% of tech workers report burnout symptomsBurnout arises from work pressures and intrinsic factors like job insecuritySetting boundaries and effective communication are crucial for preventing burnoutTune in for an honest, relatable discussion about navigating software development challenges and fostering a healthy engineering culture.LinksContext > Prompt: https://ruben.substack.com/p/context-is-all-you-need?triedRedirect=true Psychological safety episode: https://overcommitted.dev/imposter-syndrome-in-software-engineering/ Glue work article by Tanya Reilly: https://www.noidea.dog/glue Gas Town article: https://steve-yegge.medium.com/welcome-to-gas-town-4f25ee16dd04How they use Claude Code article: https://blog.sivaramp.com/blog/how-creator-of-claude-code-uses-claude-code/ HostsOvercommitted: https://overcommitted.devBethany Janos: https://github.com/bethanyj28Brittany Ellich: https://brittanyellich.comErika Eggemeyer: https://github.com/eggyhead

SummaryIn this episode of the Overcommitted Podcast, hosts Bethany, Brittany, and Erika engage in a rich conversation with Abbey Perini, a web developer and fiber artist. They explore Abbey's current projects, the intersection of fiber arts and programming, and the importance of accessibility in web development. The discussion also delves into personal experiences with ADHD, community building in both knitting and open source, and the challenges and strengths that come with neurodiversity. Abbey shares her insights on how to make coding and web development more inclusive and accessible for everyone, emphasizing the need for empathy and understanding in the tech industry.TakeawaysThere is a deep connection between fiber arts and programming.Accessibility should be a priority for all developers.Community building in knitting can inform open source practices.Accessibility is not just a front-end concern; it extends to back-end development.ADHD can present challenges but also unique strengths in coding.Flexibility in work can benefit everyone, not just those with disabilities.Negative self-talk can be harmful, and you are awesome, so stop it.Developers should focus on problem-solving skills rather than just technical tools.Creating inclusive environments in tech is essential for progress.LinksAbbey Perini’s website: https://abbeyperini.dev/Abbey on Bluesky: https://bsky.app/profile/abbeyperini.devAbbey on LinkedIn: https://www.linkedin.com/in/abbey-perini/Knitting as programming blog post: https://abbeyperini.medium.com/knitting-as-programming-9c34090e4992Web Development === Accessibility blog post: https://dev.to/abbeyperini/web-development-accessibility-f8iAn accessible dark mode toggle blog post: https://dev.to/abbeyperini/an-accessible-dark-mode-toggle-in-react-aopCoding and ADHD blog post: https://dev.to/abbeyperini/coding-and-adhd-where-we-excel-454jDesigning data-intensive applications https://www.amazon.com/Designing-Data-Intensive-Applications-Reliable-Maintainable/dp/1449373321Aria article: https://dev.to/abbeyperini/what-the-first-rule-of-aria-really-means-192eHow to do chores while drowning: https://www.amazon.com/How-Keep-House-While-Drowning/dp/1668002841/ref=sr_1_1?crid=14ND3S4IR3YLG&dib=eyJ2IjoiMSJ9.ue6gifKzpUZ5byIrJ4RUyA.9EOnSDfKG5rpl9Or07gVfVfYityMMWTqBEL4EAsN1Mw&dib_tag=se&keywords=how+to+do+chores+while+drowning&qid=1766080922&s=books&sprefix=how+to+do+chores+while+drowning%2Cstripbooks%2C83&sr=1-1Ask Jan: https://askjan.org/Study: ADHD powerful strengths - https://scitechdaily.com/adhd-isnt-just-a-deficit-new-study-reveals-powerful-psychological-strengths/HostsOvercommitted: https://overcommitted.devBethany Janos: https://github.com/bethanyj28Brittany Ellich: https://brittanyellich.comEggyhead: https://github.com/eggyhead

SummaryIn this episode, the hosts meet with Christina Martinez, a developer experience engineer from Resend, who shares insights on her creative process and current projects. She shares her delight in building silly software and how she's using that to learn in her current role.TakeawaysChristina is the creative mind behind the Gen Z Babel plugin.She also developed the Swift commits tool.Taking existing tutorials and adding a creative twist can make them more fun.Continuous development is important at all parts of your career.LinksChristina Martinez: https://christinacodes.devSilly Software Club: https://sillysoftware.clubResend: https://resend.com/Gen Z slang Babel plugin: https://www.instagram.com/reel/Cxvwz76vBus/ | https://github.com/christina-de-martinez/babel-plugin-glowup-vibesTaylor Swift themed commit linting tool: https://youtube.com/shorts/eOS5Q2I9LHM?si=LC8JVUKTkLgwKtDF | https://github.com/christina-de-martinez/swift-commitsCodeTV & Mux's Worst Video Player Competition: https://www.mux.com/blog/actual-worst-video-playerReact Miami: https://www.reactmiami.com/HostsOvercommitted: https://overcommitted.devBethany Janos: https://github.com/bethanyj28Brittany Ellich: https://brittanyellich.comEggyhead: https://github.com/eggyhead

SummaryIn this episode of the Overcommitted Podcast, hosts Brittany and Bethany with guest Bassem Dghaidi discuss a range of topics from Bassem's current learning journey in system design to his diverse career path at GitHub. They explore the value of experience over formal education, the challenges of microservices, and the importance of practical knowledge in software engineering. Bassem shares insights from his technical content creation, his philosophy as a de-influencer in the tech space, and memorable conversations with industry leaders. TakeawaysBassem's career has included various roles, enhancing his perspective.Experience in different roles provides a broader understanding of software engineering.Education is valuable, but practical experience often outweighs formal credentials.Bootcamps can bridge the gap for graduates lacking practical skills.Bassem's Git content aims to demystify complex concepts.Microservices can complicate development if implemented prematurely.Content creation in tech requires balancing depth with audience engagement.LinksBassem Dghaidi: https://linktr.ee/glich.streamBeyond Coding podcast episode: https://www.youtube.com/watch?v=LeUUxLRdvho Practical System Design Waitlist: https://maven.com/forms/b69857Kamran Ahmed's site: https://roadmap.shGhostty: https://ghostty.org/Catppuccin themes: https://catppuccin.com/Chezmoi: https://www.chezmoi.io/Tmux: https://github.com/tmux/tmux/wikiBethany's dotfiles: https://github.com/bethanyj28/dotfilesHostsOvercommitted: https://overcommitted.devBethany Janos: https://github.com/bethanyj28Brittany Ellich: https://brittanyellich.com

SummaryIn this episode of the Overcommitted Podcast, host Erika and co-host Brittany Ellich welcome Tammy Metz, a software engineer at GitHub, who shares her unique journey from teaching and library science to software engineering. The conversation explores the challenges of transitioning careers, the importance of transferable skills, and the value of mentoring in the tech industry. Tammy discusses her involvement in the Women to Women Mentoring Program, offering insights into common struggles faced by students and the significance of giving back. The episode concludes with a fun segment where the hosts share their unexpected teaching skills.TakeawaysTammy transitioned from a librarian to a software engineer.Non-traditional paths can lead to successful careers in tech.Soft skills from teaching are valuable in engineering roles.Job searching can be challenging for career switchers.Mentoring can provide guidance and support to students.It's common for students to feel lost in their career paths.Volunteering can fit into busy schedules and be rewarding.Career paths are often not linear and can change over time.LinksTammy Metz on LinkedIn: ⁠https://www.linkedin.com/in/tammy-metz/⁠Girls Who Code: https://girlswhocode.com/Woman to Woman Mentoring: https://www.womantowomanmentoring.org/HostsOvercommitted: https://overcommitted.devBrittany Ellich: https://brittanyellich.comEggyhead: https://github.com/eggyhead

SummaryIn this episode of the Overcommitted Podcast, hosts Bethany, Brittany, and Erika are joined by Cassidy Williams, Senior Director of Developer Advocacy at GitHub. They discuss Cassidy's journey in the Developer Relations (DevRel) space, her philosophy of lifting others as she climbs, and the evolution of DevRel in the tech industry. Cassidy shares insights on content creation, the importance of community, and her personal experiences with mentorship. The conversation also touches on the challenges and changes in the DevRel landscape, as well as Cassidy's passion for keyboards and her dream typing experience.TakeawaysFeedback, even when rough, is a valuable gift for growth.DevRel is evolving, adapting to new technologies and community needs.Companies should prioritize understanding the developer mindset over follower counts.Listening to developers is crucial for effective advocacy and content creation.Human problems in tech are often more complex than coding challenges.Cassidy's journey showcases the blend of engineering and advocacy roles.Mentorship plays a significant role in career development and guidance.LinksCassidy’s website: https://cassidoo.co/Microjournal Blog Post: https://cassidoo.co/post/micro-journal/Keycaps: https://drop.com/buy/drop-dsa-astrolokeys-keycaps-by-sailorhg-and-cassidoo?defaultSelectionIds=966968Cassidy’s mechanical keyboard recs: https://github.com/cassidoo/ama?tab=readme-ov-file#what-mechanical-keyboard-should-i-buyHostsOvercommitted: https://overcommitted.devBethany Janos: https://github.com/bethanyj28Brittany Ellich: https://brittanyellich.comEggyhead: https://github.com/eggyhead

SummaryIn this episode of the Overcommitted Podcast, hosts Brittany, Bethany, and Erika engage in a deep conversation with Piotr Sarna, co-author of 'Writing for Developers.' They explore the journey of co-authoring a book, the importance of writing in engineering, and the challenges and joys of technical writing. The discussion also touches on the significance of blogging as a continuation of learning and sharing knowledge, as well as the role of writing culture in engineering teams. The crew kicks off the next book club, where the Overcommitted engineers will be reading Writing for Developers together over the next 2 months!TakeawaysWriting a book can be seen as a series of extended blog posts.There is a gap in resources for writing engaging blog posts for developers.Good writing in tech should have an educational aspect.Writing culture in engineering teams enhances clarity and collaboration.The book 'Writing for Developers' fills a niche in technical writing resources.Embracing cringe-worthy writing experiences is part of the learning process.LinksPiotr Sarna on LinkedIn: https://www.linkedin.com/in/sarna-dev/Cynthia Dunlop on LinkedIn: https://www.linkedin.com/in/cynthiadunlop/Piotr and Cynthia's first book: Database performance at scale: https://bookshop.org/p/books/database-performance-at-scale-a-practical-guide-cynthia-dunlop/f384c1f0d973803c?ean=9781484297100&next=t Writing for Developers book: https://bookshop.org/p/books/writing-for-developers-blogs-that-get-read-cynthia-dunlop/af343340c60cd806?ean=9781633436282&next=tWrite that blog!: https://writethat.blog/Writing for Developers GitHub Repo: https://github.com/scynthiadunlop/WritingForDevelopersBookDiscord community for Overcommitted: https://discord.gg/fxvEjs7fHostsOvercommitted: https://overcommitted.devBethany Janos: https://github.com/bethanyj28Brittany Ellich: https://brittanyellich.comEggyhead: https://github.com/eggyhead

SummaryIn this episode of the Overcommitted Podcast, hosts Bethany, Brittany, and Erika engage in a deep conversation with Jason Lengstorf about the concept of being unreasonable in the tech industry. Jason shares his journey of embracing unreasonableness to pursue big ideas, the importance of community and networking, and how to navigate risks in career decisions. They discuss the value of non-traditional backgrounds in tech, the process of learning and consolidating information, and the creative approaches that can lead to innovative projects. The conversation wraps up with Jason sharing his future projects and reflections on the tech landscape.TakeawaysBeing unreasonable and having big audacious goals can lead to unexpected opportunities.Surround yourself with ambitious people that can inspire growth.Recognize when to pivot in your career.Networking is often more valuable than formal education.Learning is an active process, not just passive consumption.Creative coding can lead to innovative solutions.Take (calculated) risks. It can help you achieve your goals.Community support is crucial in navigating career changes.Being slow to adopt new technologies might not be a bad thing.LinksJason Lengstorf: https://jason.energyCodeTV: https://codetv.devAll things open talk: https://www.youtube.com/watch?v=goVNPN6fVwQBytes.dev: https://bytes.devChar Stiles: https://www.instagram.com/charstilesBuiltin: https://builtin.comHostsOvercommitted: https://overcommitted.devBethany Janos: https://github.com/bethanyj28Brittany Ellich: https://brittanyellich.comEggyhead: https://github.com/eggyhead

SummaryIn this episode of the Overcommitted Podcast, Erika and Brittany discuss the evolving landscape of AI agents and their implications for security and identity management. Joined by expert Dan Moore, they explore the challenges posed by non-deterministic agents, the importance of granular permissions, and the need for developers to be aware of security practices as AI technology advances. The conversation also touches on industry standards, the role of developers in navigating these changes, and personal reflections on the future of AI.TakeawaysAI agents are changing the landscape of software development.Non-deterministic agents present new security challenges.Granular permissions are essential for securing AI agents.Developers must be aware of security practices in AI.Industry standards for AI security are still evolving.Separation of concerns can enhance security for agents.The role of identity and authorization is critical in AI.Business implications of AI agents are significant.Developers should stay close to business needs and problem-solving.The future of AI will require new skills and awareness. LinksDan Moore on LinkedIn: www.linkedin.com/in/mooreds/ Dan Moore on Bluesky: https://bsky.app/profile/mooreds.comSimon Willison - The Lethal Trifecta: https://simonwillison.net/2025/Jun/16/the-lethal-trifecta/ FusionAuth: https://fusionauth.io/ AGNTCY: https://agntcy.org/Amazon Bedrock AgentCore: https://aws.amazon.com/bedrock/agentcore/ FusionAuth Guide to OAuth: https://fusionauth.io/articles/oauth/modern-guide-to-oauth MCP and OAuth: https://aaronparecki.com/2025/04/03/15/oauth-for-model-context-protocol MCP Specification: https://modelcontextprotocol.io/specification/2025-06-18/basic/authorization HostsOvercommitted: https://overcommitted.devBrittany Ellich: https://brittanyellich.com Eggyhead: https://github.com/eggyhead

SummaryJoin us for a conversation with Kate Holterhoff, an industry analyst at Redmonk who tracks developer trends from Reddit threads to conference halls. Kate shares her unique journey from earning a PhD in Victorian literature to becoming a self-taught developer and analyst, and discusses Redmonk's "new kingmakers" philosophy that recognizes developers as key decision-makers in tech adoption. We explore current industry trends including JavaScript bundlers, the real story behind AI and developer jobs, why communication skills matter as much as technical expertise, and her experiments with vibe coding across different IDEs.TakeawaysDeveloper-led adoption is the future - Redmonk's "new kingmakers" philosophy recognizes that developers, not executives, are increasingly making purchasing decisions for development tools and platforms.AI tools are becoming standard practice - Most developers now use AI code assistants and agentic IDEs, forcing organizations to adapt with proper guardrails and company plans rather than fighting adoption.AI isn't taking jobs (yet) - Current tech layoffs are more attributable to post-ZIRP (zero-interest-rate phenomenon) economics and offshoring than AI displacement, though AI has become a convenient scapegoat.JavaScript is getting massive - The recent explosion of bundlers like TurboPack, Vite, RS Pack, and Rolldown signals that JavaScript packages have grown significantly since Webpack's creation 10 years ago.Industry analysts live in developer watering holes - Understanding real developer sentiment means spending time where developers actually talk: Reddit, Hacker News, Bluesky, conferences, and podcasts.Communication skills are as critical as technical skills - Engineers who can bridge technical expertise with business communication and customer interaction have significant advantages in their careers.Alternative paths into tech are valuable - Kate's journey from Victorian literature PhD to developer analyst shows how diverse backgrounds bring unique perspectives to understanding technology and its cultural impact.Teaching can make coding accessible - Using engaging content like comic books, steampunk, and Victorian literature can make technical concepts more approachable and help students see connections across disciplines.Vibe coding is promising but unpredictable - AI-powered development tools show incredible potential but remain inconsistent, with success depending on unclear factors like IDE choice, prompting technique, and model capabilities.We need more casual learning communities - The tech industry would benefit from more informal, non-commercial spaces for developers to share experiences, especially around emerging technologies like vibe coding.LinksThe Monkcast: https://redmonk.com/blog/2023/12/07/the-monkcast/Kate on LinkedIn: https://www.linkedin.com/in/kateholterhoff/Kate on Bluesky: https://bsky.app/profile/kateholterhoff.comDwarkesh podcast with Andrej Karpathy: https://www.dwarkesh.com/p/andrej-karpathyHosts:Bethany Janos: https://github.com/bethanyj28Brittany Ellich: https://brittanyellich.com

SummaryIn this episode, Matt Sinclair, former partner and VP of Engineering at BCG Digital Ventures, explores the critical role of storytelling in effective leadership and shares his journey from building high-performance payment systems to coaching the next generation of engineering leaders. The conversation covers Matt's passion for Elixir as "the most future-proof and AI-aligned language," diving deep into functional programming, immutable data structures, and how modern coding assistants like Claude Code are revolutionizing developer productivity. Matt emphasizes that the first job of leadership is to tell a compelling story that inspires smart people to collaborate, while the art of good management lies in getting out of the way and letting talented engineers solve problems their own way.TakeawaysLeadership starts with storytelling: The primary job of leadership is explaining why smart people should get out of bed and contribute to your mission, because without a good story, people will create their own narrativesFunctional programming improves code quality: Immutable data structures and pure functions eliminate approximately 50% of common bugs and make code easier to test and reason aboutElixir offers comprehensive out-of-the-box solutions: Unlike other tech stacks requiring multiple tools (Kubernetes, Redis), Elixir provides a complete ecosystem that reduces decision fatigue and technical complexityAI-assisted coding amplifies productivity: Using Claude Code with Elixir can make a single developer feel like they have a team of five engineers, especially when working with functional programming's predictable patternsManagement should focus on "what," not "how": Leaders should collaborate with their teams to determine objectives, then trust smart people to figure out implementation details on their ownProgramming language choice impacts team quality: There's a strong correlation between functional programming adoption and high-quality software engineers, possibly due to the steeper learning curve and problem-solving mindset requiredDeveloper joy matters for sustainability: Working with languages that feel elegant and "just click" reduces exhaustion and maintains long-term passion for coding throughout a careerFunctional code is LLM-friendly: Pure functions with no side effects make it dramatically easier for AI coding assistants to reason about, refactor, and improve code automaticallyUpfront design time pays dividends: Modern AI-assisted development enables more thorough design discussions and rubber duck debugging sessions that lead to better architecture before implementation beginsCombat surveillance capitalism through decentralization: The future of the web should return to RSS feeds, web rings, and federated networks of special interest communities rather than algorithm-driven data monopolies.LinksMatt's Website: https://matthewsinclair.com/Matt Sinclair on Medium: https://matthewsinclair.medium.com/ Intent: https://github.com/matthewsinclair/intentI'm a software engineer - What next? podcast: https://whatnext.dev/An elegant puzzle by Will Larson: https://www.goodreads.com/author/show/6872433.Will_LarsonElixir: https://elixir-lang.org/Laksa: https://laksa.io/Hosts:Bethany Janos: https://github.com/bethanyj28Brittany Ellich: https://brittanyellich.comEggyhead: https://github.com/eggyhead

SummaryIn this episode of Overcommitted, hosts Erika and Brittany interview Adrienne Braganza, the author of the book Looks Good to Me. The conversation delves into the critical role of communication in code reviews, emphasizing that misunderstandings often lead to issues. It highlights the importance of understanding the purpose behind code reviews rather than just focusing on tools and speed.TakeawaysMisunderstandings are at the heart of code reviews.It's important to understand the purpose of code reviews.Focusing on tools can distract from the main goals.Collaboration is key in software development.Clear communication can prevent many issues.Taking time to reflect on processes is valuable.Agreeing on objectives enhances team alignment.Code reviews should foster learning and improvement.Understanding each other's perspectives is crucial.Effective communication leads to better outcomes.LinksAdrienne’s Website: https://adrienne.io/Adrienne on Bluesky: https://bsky.app/profile/abt.bsky.socialAdrienne on LinkedIn: https://www.linkedin.com/in/adriennetacke/Book: Looks Good to Me: https://www.manning.com/books/looks-good-to-me HostsOvercommitted Website: https://overcommitted.devBrittany Ellich: https://brittanyellich.comEggyhead: https://github.com/eggyhead

SummaryIn this episode of the Overcommitted Podcast, host Bethany and co-hosts Erika and Brittany welcome Rick Turoczy, a veteran in the Portland tech startup scene. They discuss Rick's journey from a hobbyist developer to a key supporter of startup founders, the unique culture of Portland's tech community, and the importance of mental health for founders. Rick shares insights on the challenges of being a founder, the evolution of startup culture, and the role of PIE in supporting startups. The conversation also touches on local recommendations and the vibrant community in Portland.TakeawaysLearning how to learn is a crucial skill for navigating the startup world.Portland's tech scene is characterized by a unique culture of humility and creativity.Founders often face significant mental health challenges and need support systems.The PIE initiative aims to foster collaboration between startups and established organizations.Mistakes are a part of the learning process for founders, and experimentation is key.The startup landscape has evolved, making it easier to build products but harder to sell them.The challenges of being a founder are often underestimated, leading to burnout.Understanding the difference between wanting to build a product and wanting to build a company is crucial for founders.LinksRick's LinkedIn: https://www.linkedin.com/in/turoczy/Rick's Bluesky: https://bsky.app/profile/turoczy.bsky.socialRick's YouTube: https://www.youtube.com/@turoczy_PIE Cookbook: https://github.com/piepdx/pie-cookbook/blob/master/docs/pie-cookbook-0.9.mdPowell’s City of Books: https://www.powells.com/bookstore/powells-city-of-books?srsltid=AfmBOoqCGKjvdY5g6DowX0ReNqRlLARxeI5WKwGyc8P0Pq3O8j9Fd0NQ Deadstock Coffee: https://deadstockcoffee.com/?srsltid=AfmBOopNiNhvGUigNJxASlm97jUCcSb6l36xCJ6sZF6mRIkyIseejJQyPodcast recommendation from Erika: ​​https://podcasts.apple.com/us/podcast/237-mistake-it-till-you-make-it-learn-faster-and-fail-smarter/id1494989268?i=1000732814742HostsBethany Janos: https://github.com/bethanyj28Brittany Ellich: https://brittanyellich.comEggyhead: https://github.com/eggyhead

SummaryIn this episode of the Overcommitted Podcast, Erika and Brittany delve into the concept of flow state in software development, exploring its significance for productivity and job satisfaction. They share personal experiences of achieving flow, discuss the balance between challenge and skill, and highlight the importance of psychological safety and team dynamics. The conversation also touches on managing interruptions, the role of pair programming, and strategies for improving flow state within teams. The episode concludes with a fun quiz to engage listeners in reflecting on their own flow experiences.TakeawaysFlow state is linked to enhanced productivity and job satisfaction.A balance between challenge and skill is essential for achieving flow.Cognitive overload can hinder the ability to enter flow state.Immediate control over tasks contributes to maintaining flow.Psychological safety within teams fosters better performance.Managing interruptions is crucial for maintaining focus.Pair programming can facilitate flow but may introduce challenges.Team dynamics significantly impact individual flow experiences.Investing in tools and environments can enhance flow state.Regular reflection on flow experiences can lead to improved productivity.LinksDeveloper flow article: https://leadership.garden/developer-flow/ Podcast: Neuroscience and Developer Productivity: https://podcasts.apple.com/us/podcast/prefrontal-by-cortex/id1760813899?i=1000676601346Vibe Engineering by Simon Willison: https://simonwillison.net/2025/Oct/7/vibe-engineering/SPACE Metrics: https://getdx.com/blog/space-metrics/HostsOvercommitted Website: https://overcommitted.devBrittany Ellich: https://brittanyellich.comEggyhead: https://github.com/eggyhead

SummaryIn this episode of the Overcommitted Podcast, host Brittany Ellich and co-hosts Bethany and Erika welcome Thomas Dohmke, former CEO of GitHub. They discuss Thomas's journey in software development, pivotal moments in his career, the importance of passion and continuous learning, and advice for overcoming career stagnation. The conversation also touches on the future of software development, particularly the impact of AI, and concludes with a fun round of questions about LEGO.TakeawaysThomas grew up in East Germany and discovered coding through a school lab.His passion for software development has been a constant throughout his career.Mentorship played a crucial role in his transition from university to the automotive industry.The importance of continuous learning in a fast-paced tech environment.Developers often feel stuck in their careers, but a growth mindset can help overcome this.Asking for help and having open conversations with managers can lead to new opportunities.Reading books on engineering and leadership can provide valuable insights.AI is set to revolutionize the software development landscape again.The journey of a developer is filled with ups and downs, but passion keeps them motivated.Thomas encourages developers to embrace change and stay curious.LinksThomas on GitHub: https://github.com/ashtomThomas on LinkedIn: https://www.linkedin.com/in/ashtom/Thomas on X: https://x.com/ashtomThe Great Mental Models book: https://www.goodreads.com/book/show/44245196-the-great-mental-modelsAn Elegant Puzzle by Will Larson: https://www.goodreads.com/book/show/45303387-an-elegant-puzzleStaff Engineer by Will Larson: https://www.goodreads.com/book/show/56481725-staff-engineerThe Engineering Executive's Primer: https://www.goodreads.com/book/show/199699997-the-engineering-executive-s-primerBricklink: https://www.bricklink.com/v2/main.pageHostsBethany Janos: https://github.com/bethanyj28Brittany Ellich: https://brittanyellich.comEggyhead: https://github.com/eggyhead

SummaryIn this episode of the Overcommitted Podcast, host Erika and co-hosts Bethany and Brittany Ellich engage in a conversation with Don McKinnon, founder of Searchcraft. They discuss Don's journey in software engineering, the challenges faced while building Searchcraft, and the unique features that make it accessible for developers of all levels. The conversation also touches on the integration of AI, market competition, and the path to founding a startup, concluding with a fun segment about walkout songs.TakeawaysSearchcraft aims to reduce complexity in search infrastructure.Rust was chosen for its efficiency and performance benefits.Building Searchcraft took two years of development before launching as a product.Searchcraft allows non-technical users to manage search relevancy through a GUIAI integration is crucial for modern applications, especially in search.The market for search tools is evolving with the emergence of AI.Founding a startup involves learning and adapting to new challenges.Identifying pain points is key to developing a successful product.It's important to focus on solving real problems rather than perfection.The journey of building a product can lead to unexpected opportunities.LinksDon MacKinnon⁠⁠: https://donmackinnon.dev/Searchcraft⁠⁠: ⁠https://www.searchcraft.io/⁠Article: https://medium.com/@dmackinnon/improving-trust-in-ai-systems-432d61bef7b3HostsOvercommitted: https://overcommitted.devBethany Janos⁠⁠: https://github.com/bethanyj28Brittany Ellich⁠⁠: ⁠https://brittanyellich.com⁠Eggyhead⁠: ⁠https://github.com/eggyhead⁠

SummaryIn this episode of the Overcommitted Podcast, hosts Brittany Ellich and Erika engage with Brad Heller, co-founder and CTO of Tower, discussing his journey from software engineer to startup founder. They explore the evolution of software engineering careers, the challenges of entrepreneurship, and the skills necessary for success in the tech industry. Brad shares insights on the importance of aligning passions with work, the realities of startup life, and advice for aspiring engineers. The conversation also touches on the impact of AI on coding and the importance of understanding the fundamentals of software development.TakeawaysBrad's journey from corporate life to startups was driven by a desire for impactful work.Working at startups can provide invaluable learning experiences compared to big tech.Entrepreneurship requires aligning your passions with your work for true success.Delegating tasks is a crucial skill for founders, but often difficult to master.Understanding the entire business process is essential for engineers in startups.The tech landscape has changed, with many entering the field for financial reasons rather than passion.AI is transforming the coding landscape, but understanding the fundamentals remains critical.Networking skills developed in big tech can be beneficial in startup environments.It's important to recognize when to hire and delegate responsibilities as a founder.The romanticized view of entrepreneurship often overlooks the hard work involved.LinksBrad Heller on LinkedInTower.DevPaul GrahamWill Larson - A forty-year careerPIE PDXRick TuroczyHostsOvercommitted.devBrittany EllichEggyhead

SummaryIn this episode of the Overcommitted Podcast, hosts Bethany and Brittany discuss their experiences at recent tech conferences, including Cascadia JS and GopherCon. They reflect on their goals from the past quarter, sharing successes and challenges, and set new objectives for the upcoming quarter. The conversation also touches on the importance of community engagement and personal development in the tech industry, culminating in a fun segment where they share ideas for potential TED talks.TakeawaysThe importance of community in tech events.Reflecting on past goals helps in personal growth.Engagement in newsletters can shift focus from self-promotion to sharing others' work.Attending conferences can provide fresh insights and networking opportunities.Setting realistic goals is crucial, especially during busy times.Public speaking can be a rewarding experience despite initial anxiety.Finding enjoyment in activities is essential for long-term commitment.Quarterly retrospectives can help realign personal and professional goals.Exploring new interests can lead to unexpected opportunities.Community engagement is vital for mental well-being in remote work environments.Links⁠CascadiaJSGopherConMagnoliaConf⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Tech book club Repo⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Overcommitted Discord⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Hosts⁠⁠⁠⁠⁠Overcommitted.dev⁠⁠⁠⁠⁠⁠Bethany Janos⁠⁠⁠⁠⁠Brittany Ellich⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠

SummaryIn this episode of the Overcommited podcast, the hosts engage in a deep conversation with Indrajith Premanath, an engineer at GitHub, who shares his journey of transitioning from an individual contributor to an engineering manager during an interim manager role while his manager was on leave. Indrajith discusses the challenges and lessons learned during his six-month stint as an interim manager, emphasizing the importance of team dynamics, transparency, and personal growth. The conversation also touches on career aspirations, technical interests, and the significance of building strong relationships within a team. Indrajith offers valuable advice for future managers and reflects on his childhood aspirations, providing a well-rounded perspective on his career journey.TakeawaysThe shift from coding to management requires a change in mindset and priorities.Building relationships with team members is crucial for effective management.Transparency in decision-making fosters trust within the team.Indrajith found that he became a better individual contributor after his management experience.Understanding team members' career goals enhances team dynamics.Indrajith emphasizes the importance of long-term planning in management.He advocates for rotation programs for aspiring managers to gain experience.The role of AI in coding is changing the landscape of software development.Indrajith's childhood aspiration was to be a theater kid, not a software engineer.LinksIndrajith Premanath LinkedInCharity Majors Engineer/Manager Pendulum Article⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Tech book club Repo⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Overcommitted Discord⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Hosts⁠⁠⁠⁠Overcommitted.dev⁠⁠⁠⁠⁠⁠⁠⁠⁠Brittany Ellich⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Eggyhead⁠⁠⁠⁠⁠⁠⁠⁠Jonathan Tamsut⁠

SummaryIn this episode of the Overcommitted podcast, host Brittany Ellich and co-hosts Erika, Bethany, and Jonathan Tamsut engage in a conversation with Annie Sexton, a developer advocate at fly.io. They explore Annie's unique journey into developer advocacy, her approach to education and community building, and the importance of teaching techniques in the tech industry. The discussion also delves into the role of AI in learning and development, as well as personal interests outside of software engineering, highlighting the multifaceted lives of software professionals.TakeawaysAnnie Sexton transitioned from software engineering to developer advocacy through her passion for education.Developer advocacy involves community building, education, and marketing to developers.Education is a powerful tool for building trust with an audience.Asking basic questions is crucial for effective teaching and learning.AI can be a valuable resource for research and learning, but fact-checking is essential.Understanding the audience's knowledge level is key to effective communication.Annie emphasizes the importance of storytelling in education and advocacy.The journey to becoming a developer advocate can be unconventional and varied.Engaging content can attract a wider audience beyond just product promotion.Personal interests and hobbies contribute to a well-rounded life as a software engineer.Links⁠fly.iofly.io YouTube channelAnnie’s YouTube channelBook: Deep Learning A Visual ApproachBook: A City on MarsShow/Book: The ExpanseBluesky: @anniesexton.comBluesky: for Annie’s comics⁠⁠⁠⁠⁠⁠⁠⁠Tech book club Repo⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Overcommitted Discord⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Hosts⁠⁠Overcommitted.dev⁠⁠⁠Bethany Janos⁠⁠Brittany Ellich⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Eggyhead⁠⁠⁠⁠Jonathan Tamsut

SummaryIn this episode of the Overcommitted Podcast, Brittany, Erika, and Jonathan delve into the complex relationship between software engineering, social media, and ethics. They explore their personal experiences with social media, the evolution of algorithms, and the monetization strategies that have transformed platforms into profit-driven entities. The conversation highlights the societal impacts of social media, particularly on mental health, and discusses the responsibilities of engineers in creating user-centered designs. They also consider potential regulatory measures, such as profit caps, and the need for a code of ethics in software engineering to mitigate harm.TakeawaysThe promise of social media was to increase social connection.Algorithms have shifted from social interaction to maximizing engagement.Monetization strategies have created a creator economy.Social media platforms often prioritize profit over user well-being.The societal impact of social media is profound and concerning.Engineers have a responsibility to consider the human impact of their work.Regulation may be necessary to address the harms of social media.Profit caps could help redirect funds towards community projects.An information diet can help mitigate negative effects of social media.A code of ethics for software engineers could guide responsible development.LinksVideo: Why everyone is quitting social mediaCareless PeopleInterview on information diet with HerariBill in 1996ACM Code of Ethics⁠⁠⁠⁠⁠⁠⁠Tech book club Repo⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Overcommitted Discord⁠⁠⁠⁠⁠⁠⁠⁠⁠Hosts⁠Overcommitted.dev⁠⁠⁠Brittany Ellich⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Eggyhead⁠⁠Jonathan Tamsut

SummaryJoin Bethany, Erika, and Brittany as they dive into the art of storytelling in tech — and discover why your next presentation or documentation doesn't have to be boring! From the visual wizardry of Astro's docs to Julia Evans' beloved wizard zines, this episode explores how great technical communication combines compelling narratives with clear information. Whether you're crafting a lightning talk (like Bethany's upcoming NeoVim presentation at GopherCon!), writing PR descriptions that tell a story, or trying to hook your audience from the very first sentence, you'll learn practical techniques for making complex concepts engaging and accessible. Plus, hear why AI-generated content might be "an act of war" on people's time, discover the power of self-deprecation and visual storytelling, and enjoy a hilarious developer-themed mad libs featuring thrown staplers and flappy outcomes. Perfect for anyone who wants to level up their technical communication game!TakeawaysTechnical storytelling can make complex concepts relatable.Visual elements enhance engagement in documentation and presentations.Approachability is key for technical documentation.Understanding the audience's needs is crucial for effective communication.A strong hook captures attention in presentations.Emotional connections can enhance technical storytelling.Documentation should be clear and scannable for users.Using a glossary can help bridge knowledge gaps in presentations.Empathy towards the audience improves the storytelling experience.AI tools should enhance, not replace, human storytelling.Links⁠Astro docsJulia EvansGitHub Blog Post: Documentation done right - A developer's guide⁠⁠⁠⁠⁠⁠Tech book club Repo⁠⁠⁠⁠⁠⁠⁠⁠⁠Overcommitted Discord⁠⁠⁠⁠⁠⁠⁠⁠HostsOvercommitted.dev⁠⁠Bethany Janos⁠Brittany Ellich⁠⁠⁠⁠⁠⁠⁠⁠⁠Eggyhead⁠

SummaryIn this episode of the Overcommitted Podcast, the hosts discuss the role of gamification in software development, exploring how it can influence learning, creativity, and project management. They delve into the psychological aspects of fear of failure, the importance of trial and error, and the balance between external and internal motivation. The conversation also touches on the potential trade-offs of gamification and the significance of celebrating efforts within a team culture. The episode concludes with a fun segment where the hosts share their favorite video game characters.TakeawaysGamification can reduce the fear of failure in learning.The Super Mario Effect illustrates how failure can be framed positively.Trial and error is essential in software engineering.Gamification strategies can include sandbox environments and quests.Balancing external and internal motivation is crucial for engagement.Metrics can sometimes misrepresent true productivity and impact.Gamification can lead to unintended consequences if not managed carefully.LinksFeel good productivity⁠⁠⁠⁠⁠Tech book club Repo⁠⁠⁠⁠⁠⁠⁠Overcommitted Discord⁠⁠⁠⁠⁠⁠⁠Hosts⁠⁠⁠⁠⁠⁠⁠Overcommitted.devBethany JanosBrittany Ellich⁠⁠⁠⁠⁠⁠⁠Eggyhead⁠Jonathan Tamsut⁠

SummaryIn this episode of the Overcommitted Podcast, hosts Jonathan, Brittany, and Erika delve into the exciting world of AI agents. They explore the potential of AI agents in software engineering, their functionality, and the challenges of building and categorizing them. The conversation also touches on the future of job searching and personal development through AI, emphasizing the need for a more personalized and effective approach to technology and learning.Takeaways- AI agents represent a new paradigm in problem-solving.- AI agents can offload cognitive tasks.- User experience with AI agents needs to be redefined.- AI agents can be tailored to specific domains for better results.- Defining success metrics is crucial when building AI agents.- Job searching processes are outdated and need innovation.- AI can assist in personal development and career growth.- Customizable search engines could enhance information retrieval.- The role of human bias in hiring processes is significant.Links⁠Building effective agents⁠Balanced Engineer NewsletterPlausible SchemesEmbedding modelsObsidian Copilot⁠⁠⁠⁠Tech book club Repo⁠⁠⁠⁠⁠Overcommitted Discord⁠⁠⁠⁠⁠⁠Hosts⁠⁠⁠⁠⁠⁠Overcommitted.devBrittany Ellich⁠⁠⁠⁠⁠⁠Eggyhead⁠Jonathan Tamsut⁠

SummaryIn this episode of the Overcommitted Podcast, the hosts discuss the concept of personal branding for software developers. They explore what a personal brand means, the importance of authenticity, and how to build visibility within the tech community. The conversation highlights the balance between promoting oneself and staying true to one's values, as well as the challenges faced by individuals in a male-dominated industry. The hosts also share their thoughts on admired personal brands in tech, emphasizing the significance of community and mentorship.TakeawaysPersonal branding encompasses your values and how you want to be perceived.It's important to be authentic when developing a personal brand.Building a personal brand can help in career advancement and visibility.Sharing your work and interests is crucial for building a personal brand.The perception of personal branding can differ based on gender and identity in the workplace.It's valuable to recognize what you want to be known for in your career.Engaging with your community can enhance your personal brand.Maintaining authenticity while sharing your work is a challenge for many.Finding platforms that align with your values is important for personal branding.Admiring others' personal brands can inspire your own branding journey.LinksStaff Engineer by Will LarsonJulia EvansCassidy WilliamsGergely OroszCharity Majors⁠⁠⁠Tech book club Repo⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Overcommitted Discord⁠⁠⁠⁠⁠Hosts⁠⁠⁠⁠⁠Overcommitted.dev⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Bethany Janos⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Brittany Ellich⁠⁠⁠⁠⁠⁠⁠Eggyhead⁠⁠Jonathan Tamsut⁠

SummaryIn this episode of the Overcommitted podcast, hosts Bethany, Brittany, and Erika engage with guest Nick Gerakines to explore the intricacies of the AT Protocol, its implications for user data ownership, and the evolution of social media platforms. They discuss the importance of user control, the concept of a credible exit from platforms, and the development journey of applications built on the AT Protocol. The conversation also touches on the complexities of OAuth in modern applications and the significance of community involvement in open source projects.TakeawaysNick Gerakines is a software engineer with a rich background in online education and infrastructure.AT Protocol focuses on identity and data ownership, allowing users to control their data.Decentralized identifiers (DIDs) are crucial for user identity in the AT Protocol ecosystem.User mobility is a key feature of AT Protocol, enabling users to move their data across platforms.The concept of a credible exit allows users to leave platforms without losing their data.Development on AT Protocol has been a rewarding journey for Nick, leading to innovative applications.The future of social engagement is promising with new tools and communities emerging.OAuth presents unique challenges in the context of agent-based systems.Building community and engaging in open source projects is essential for developers.Diversity of thought enhances problem-solving and innovation in technology.Links⁠⁠Connect with Nick GerakinesWhy AT Protocol blog postSmoke Signal Presentation at ATmosphere Conf⁠⁠Tech book club Repo⁠⁠⁠⁠⁠⁠⁠⁠Overcommitted Discord⁠⁠⁠⁠Hosts⁠⁠⁠⁠Overcommitted.dev⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Bethany Janos⁠⁠⁠⁠⁠⁠⁠⁠Brittany Ellich⁠⁠⁠⁠⁠Eggyhead

SummaryIn this episode of the Overcommitted Podcast, hosts Erika, Bethany, and Brittany Ellich interview Alec Breton, Cole Hartman, and Doris Wang, a mentor and two summer interns from GitHub, to discuss the importance of mentorship in tech internships. They explore what defines a successful internship, the structure of the internship program, and the dynamics of mentorship relationships. The conversation also delves into the significance of psychological safety in fostering a productive learning environment, the balance between using AI tools and personal learning, and offers advice for aspiring interns and mentors. The episode concludes with a fun segment where guests share their ideal mentors.TakeawaysA successful internship is about learning and contributing.Interns should feel comfortable asking questions.Psychological safety is crucial for growth.Being a good mentee is also important.Use AI as a tool, not a crutch.Be your authentic self in interviews.Building trust is essential in mentorship.Understanding the product is key before coding.Mentorship is about leading and learning together.Links⁠Connect with Alec BretonConnect with Cole HartmanConnect with Doris Wang⁠Tech book club Repo⁠⁠⁠⁠⁠⁠Overcommitted Discord⁠⁠⁠Hosts⁠⁠⁠Overcommitted.dev⁠⁠⁠⁠⁠⁠⁠⁠Bethany Janos⁠⁠⁠⁠⁠⁠Brittany Ellich⁠⁠⁠Eggyhead

SummaryIn this episode of the Overcommitted Podcast, host Jonathan Tamsut and co-hosts Brittany Ellich and Bethany engage in a deep conversation with Jennifer Harris, founder and CEO of Technology Management Concepts. They explore Jennifer's journey into entrepreneurship, the evolution of her role as a CEO, and the unique challenges faced by women in tech. The discussion touches on imposter syndrome, the importance of networking, and the dynamics of gender in the workplace, particularly in relation to AI and technology. Jennifer shares valuable insights and advice for women in tech, emphasizing the need for self-advocacy and the importance of building relationships. The episode concludes with reflections on the future of AI and the opportunities it presents for women in business.TakeawaysJennifer's journey began with a passion for solutions and technology.Entrepreneurship requires resilience and adaptability.Imposter syndrome is a common challenge for folks in leadership.Women often face unique challenges in the tech workplace.Self-advocacy is essential for folks in tech.Building relationships is key to professional growth.LinksConnect with Jennifer HarrisTech book club Repo⁠⁠⁠⁠Overcommitted Discord⁠⁠Hosts⁠⁠Overcommitted.dev⁠⁠⁠⁠⁠⁠Bethany Janos⁠⁠⁠⁠Brittany Ellich⁠⁠⁠⁠Jonathan Tamsut

SummaryIn this episode of the Overcommitted Podcast, Brittany Ellich and her co-hosts engage with Ross Brodbeck, a software engineer at GitHub, to explore the critical topic of software availability. They discuss the definitions of availability, reliability, and uptime, and delve into frameworks for improving availability in software systems. The conversation covers proactive versus reactive approaches to availability, the business impact of availability, and the hidden costs associated with downtime. Ross shares insights on creating effective availability programs, the role of incident commanders, and emerging technologies that may shape the future of availability in software engineering. The episode concludes with book recommendations for software engineers looking to deepen their understanding of the field.TakeawaysAvailability is subjective and varies by organization.Observability is crucial for understanding production behavior.Proactive measures can help prevent availability issues.On-call burnout is a significant cost to organizations.Understanding business needs is key to defining availability.SLOs help in measuring and reporting availability effectively.Incident commanders play a vital role in managing incidents.Game days and playbooks are essential for preparedness.Hidden costs of downtime include loss of customer trust.Emerging technologies like AI may change availability management.LinksRoss’s BlogGoogle SRE Bookhttps://sreweekly.com/https://uptime.is/Catchpoint SRE ReportSoftware engineer’s guidebookDesigning data-intensive applicationsThinking in systemsThe best software writing one - Joel on Software Algorithms to live byThe Staff EngineerClean CodePragmatic Engineer Podcast - Thomas Dhomke interviewDistributed systems by Martin van SteenPractical object-oriented design in RubyLooks Good To MeTech book club Repo⁠⁠Overcommitted Discord⁠Hosts⁠Overcommitted.dev⁠⁠⁠⁠Bethany Janos⁠⁠Brittany Ellich⁠⁠Eggyhead⁠⁠Jonathan Tamsut

SummaryIn this episode of the Overcommitted Podcast, hosts Bethany, Jonathan, Brittany, and Erika reflect on their goals for the second quarter, sharing successes and challenges. They discuss lessons learned, personal growth, and strategies for improvement. The conversation also touches on their personal interests and hobbies, culminating in an exciting announcement about the launch of the new tech book club.TakeawaysSetting specific goals can lead to increased productivity.Tracking progress helps in achieving reading goals.Adapting to life changes is crucial for maintaining focus.Defending personal boundaries is important for mental health.Finding joy in productivity can enhance overall satisfaction.Engaging in community activities can foster personal growth.Exploring new hobbies can lead to unexpected interests.Creating a routine can help in managing commitments.Reflecting on past goals can provide insights for future planning.Collaboration and discussion can enhance learning experiences.LinksFeel good productivity bookSam Who.DevThe Mind IlluminatedTech book club RepoOvercommitted DiscordHostsOvercommitted.dev⁠⁠Bethany JanosBrittany EllichEggyheadJonathan Tamsut

SummaryIn this episode of the Overcommitted Podcast, the hosts discuss the intricacies of pull requests, focusing on the reviewer mindset, crafting effective pull requests, and managing the review workflow. They share insights from Brittany's recent conference experience and delve into best practices for both reviewing and creating pull requests. The conversation highlights the importance of communication within teams, the impact of reviews, and the balance between thoroughness and efficiency in the review process. The episode concludes with a light-hearted discussion on pet peeves and positive aspects of PR reviews.TakeawaysThe impact of a review is more important than personal preferences.As a reviewer, focus on unblocking colleagues and improving code quality.Automate style checks with CI to streamline the review process.PRs should be as small as possible to reduce cognitive load.Include context in PRs to aid understanding for reviewers.Set clear expectations with your team regarding review timelines.Use PRs as a learning opportunity for both reviewers and contributors.Document decisions and discussions within PRs for future reference.Encourage a blameless culture around PR approvals.Positive feedback in reviews fosters a supportive team environment.LinksThe Balanced Engineer Newsletter: Code reviews - A how to guide: https://archives.balancedengineer.com/archive/code-reviews-a-how-to-guide/ The Balanced Engineer Newsletter: Code reviews - Writing good PRs: https://archives.balancedengineer.com/archive/code-reviews-writing-good-prs/The Balanced Engineer Newsletter: Code reviews - Managing review workload: https://archives.balancedengineer.com/archive/code-reviews-managing-review-workload/ Erika’s PR Template: https://github.com/eggyhead/obsidian-public/blob/main/templates/pr-review-note.md Ben Balter: How I manage GitHub notifications: https://ben.balter.com/2020/08/25/how-i-manage-github-notifications/ Hosts⁠Overcommitted.dev⁠Bethany Janos: ⁠https://github.com/bethanyj28⁠ Brittany Ellich: ⁠https://brittanyellich.com⁠ Eggyhead: ⁠https://github.com/eggyhead⁠Jonathan Tamsut: ⁠https://infinitely-fallible.bearblog.dev/⁠

SummaryIn this episode of the Overcommitted Podcast, hosts Jonathan Tamsut, Brittany Ellich, Bethany, and Erika delve into the predictions made by the AI Futures Project regarding the future of artificial intelligence by 2027. They discuss the potential for AI to self-improve, the implications of an AI arms race, and the importance of regulation in ensuring safe AI development. The conversation also touches on the risks of AI misalignment with human values, the future of work in an AI-driven world, and the influence of corporate interests on AI regulation. The hosts conclude by assessing the probability of existential risks posed by AI, known as P-Doom, and the need for a code of ethics in the tech industry.TakeawaysThe AI Futures Project predicts significant advancements in AI by 2027.AI models may train themselves, leading to recursive self-improvement.Regulation is crucial to prevent potential risks associated with AI.Misalignment of AI with human values poses serious risks.The future of work may shift towards managing AI agents rather than coding.Corporate interests may hinder the safe development of AI technologies.The concept of P-Doom assesses the existential risks of AI.A code of ethics for software developers could be more effective than government regulation.The conversation highlights skepticism towards aggressive AI predictions.The hosts express concerns about the implications of AI on society. LinksAI 2027Scaling laws for neural language modelsP doom websiteThe next big idea podcastThe illusion of thinking paperHostsOvercommitted.devBethany Janos: https://github.com/bethanyj28 Brittany Ellich: https://brittanyellich.com Eggyhead: https://github.com/eggyheadJonathan Tamsut: https://infinitely-fallible.bearblog.dev/

SummaryIn this episode of the Overcommitted Podcast, hosts Brittany Ellich, Jonathan Tamsut, Bethany Janos, and Erika discuss their experiences with tech events, including how to choose which events to attend, strategies for networking, maximizing time at conferences, and the value of speaking and volunteering. They share personal anecdotes and tips for making the most out of these opportunities while also addressing the challenges of social anxiety and the importance of setting boundaries. The conversation wraps up with some light-hearted unpopular opinions about tech events.Links⁠GopherconMicrosoft buildAll things openDefconEpic Web ConfGopherconEUTakeawaysChoosing the right tech events is crucial for personal growth.Networking can be approached with prepared questions to ease anxiety.It's important to recognize that everyone at events wants to connect.Setting boundaries at conferences can help manage social fatigue.Leaving a talk that isn't engaging is perfectly acceptable.Collecting swag is a fun part of attending conferences.Speaking at events can provide unique opportunities for travel and learning.Volunteering at conferences offers valuable insights into customer perspectives.Finding a balance between attending talks and networking is key.Enjoying yourself at events should be a priority.Hostsovercommitted.devBethany Janos: https://github.com/bethanyj28Brittany Ellich: https://brittanyellich.comEggyhead: https://github.com/eggyheadJonathan Tamsut: https://infinitely-fallible.bearblog.dev/

SummaryIn this episode of the Overcommitted Podcast, hosts Bethany, Brittany, and Erika discuss their experiences with the book 'Thinking in Systems' by Donella Meadows. They explore the concepts of systems thinking and its applications in software engineering, team dynamics, and societal issues. The conversation delves into the importance of feedback loops, user experience, and the impact of organizational structures on individual performance. The hosts also reflect on their book club experience, sharing insights on how to foster engaging discussions and learning opportunities.LinksThinking in Systems⁠⁠The point of the system is what it does - Anil Dash⁠Just for fun⁠Changelog episode about COBOL⁠TakeawaysThe book 'Thinking in Systems' is approachable and easy to read.Systems thinking can be applied to various fields, not just software engineering.Feedback loops are crucial in understanding how systems function.Understanding the goals of a system can help identify problems.Organizational systems can be challenging to change compared to software systems.The book club format enhances learning and engagement.It's important to recognize the motivations within a system.Technical discussions can be enriched by diverse perspectives.Hostsovercommitted.devBethany Janos: https://github.com/bethanyj28Brittany Ellich: https://brittanyellich.comEggyhead: https://github.com/eggyhead

This week the crew chats with Hirsch Singhal, Staff Product Manager at GitHub, about effective collaboration between product and engineering. LinksHirsch Singhal's Bluesky: https://bsky.app/profile/hpsin.netHirsch Singhal's LinkedIn: https://www.linkedin.com/in/hirsch-singhal/Domain-Driven Design: https://www.amazon.com/Domain-Driven-Design-Tackling-Complexity-Software/dp/0321125215 Hosts⁠⁠⁠⁠Overcommitted.dev⁠⁠⁠⁠Bethany Janos: ⁠⁠⁠⁠https://github.com/bethanyj28⁠⁠⁠⁠Brittany Ellich: ⁠⁠⁠⁠https://brittanyellich.com⁠⁠⁠⁠Eggyhead: ⁠⁠⁠⁠https://github.com/eggyhead⁠⁠⁠Jonathan Tamsut: ⁠⁠https://jtamsut.substack.com⁠⁠

The crew chat about what we're learning right now and how we learn.LinksPARA: https://fortelabs.com/blog/para/The Art of Visual Design: https://www.artofvisualdesign.com/ Math Academy: https://www.mathacademy.com/Deep Learning from scratch: https://www.oreilly.com/library/view/deep-learning-from/9781492041405/Kaggle competitions: https://www.kaggle.com/A Philosophy of Software Design: https://blog.pragmaticengineer.com/a-philosophy-of-software-design-review/ The Feynman Technique: https://fs.blog/feynman-technique/The Bradfield School: csprimer.comExecute program: https://www.executeprogram.com/ NotebookLM from Google: https://notebooklm.google.com/ The Software Engineer's Guidebook: https://www.engguidebook.com/Pachinko: https://www.goodreads.com/book/show/34051011-pachinkoPiranesi: https://www.goodreads.com/book/show/50202953-piranesiThinking in Systems: https://www.amazon.com/How-Solve-Mathematical-Princeton-Science/dp/069111966XAlgorithms to live by: https://algorithmstoliveby.com/The Chaos Machine: https://www.goodreads.com/book/show/58950736-the-chaos-machineCosmos by Carl Sagan: https://www.goodreads.com/book/show/55030.CosmosHow to Solve it: https://www.goodreads.com/book/show/192221.How_to_Solve_ItThe little book of aliens: https://www.goodreads.com/book/show/123018903-the-little-book-of-aliensDesigning Data Intensive Applications: https://www.goodreads.com/book/show/23463279-designing-data-intensive-applicationsHosts⁠⁠⁠Overcommitted.dev⁠⁠⁠Bethany Janos: ⁠⁠⁠https://github.com/bethanyj28⁠⁠⁠Brittany Ellich: ⁠⁠⁠https://brittanyellich.com⁠⁠⁠Eggyhead: ⁠⁠⁠https://github.com/eggyhead⁠⁠Jonathan Tamsut: ⁠https://jtamsut.substack.com⁠