Tech Lead Journal

Are long code review cycles killing your engineering team’s velocity? Learn how top engineering teams are shipping code faster without sacrificing quality.In this episode, Greg Foster, CTO and co-founder of Graphite, discusses the evolution of code review practices, from the fundamentals of pull requests to the future of AI in code review workflows. He shares the secrets behind how the Graphite team became one of the most productive engineering teams by leveraging techniques like small code changes and stacked PRs (pull requests).Key topics discussed:The evolution of code review from bug-hunting to knowledge sharingBest practices for PRs and why small PRs get better feedbackHow stacked PRs eliminate waiting time in development workflowsThe rise of AI in the code review processWhy AI code review works best as an automated CI checkHow Graphite achieves P99 engineering productivityHiring engineers in the age of AI-assisted codingTimestamps:(00:00) Trailer & Intro(02:21) Career Turning Points(05:11) Now is The Golden Time to Be in Software Engineering(09:08) The Evolution of Code Review in Software Development(14:59) The Popularity of Pull Request Workflow(21:01) Pull Request Best Practices(26:17) The Stacked PR and Its Benefits(34:07) How Graphite Ships Code Remarkably Fast(40:03) The Cool Things About AI Code Review(45:23) Graphite’s Unique Recipes for Engineering Productivity(50:55) Hiring Engineers in the Age of AI(55:31) 2 Tech Lead Wisdom_____Greg Foster’s BioGreg Foster is the CTO and co-founder of Graphite, an a16z and Anthropic-backed company helping teams like Snowflake, Figma, and Perplexity ship faster and scale AI-generated code with confidence. Prior to Graphite, Greg was a dev tools engineer at Airbnb. There, he experienced the impact of robust internal tooling on developer velocity and co-founded Graphite to bring powerful, AI-powered code review to every team. Greg holds a BS in Computer Science from Harvard University.Follow Greg:LinkedIn – linkedin.com/in/gregmfosterX – x.com/gregmfosterEmail – greg@graphite.devGraphite – graphite.devGraphite X – x.com/withgraphiteLike this episode?Show notes & transcript: techleadjournal.dev/episodes/231.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

Struggling with technical debt and code quality? Learn how a technical coach can help your team level up.In this episode, Emily Bache, a Samman technical coach, shares her proven method for building better engineering teams through structured learning and collaborative coding. We explore ensemble programming, learning hours, and why AI makes fundamental engineering practices more important than ever.Key topics discussed:The role of a Technical Coach and the Samman Method explainedHow AI amplifies good engineering practices instead of replacing themHow to use ensemble programming to achieve single-piece flowRunning effective ensemble sessions and avoiding common failure modesWhy learning is part of the work, not only a side activityWhy pull requests should not be the primary tool for mentoring junior developersThe dangerous trend of “vibe coding” with AI toolsTimestamps:(00:00) Trailer & Intro(02:22) Career Turning Points(03:23) Being Part of Modern Engineering YouTube Channel(04:27) The Role of a Technical Coach(05:42) The Impact of AI on Technical Coaching(08:20) Sofware Engineering is a Learning Process(09:55) Optimizing Learning With Samman Method(11:40) The Samman Method: Ensemble (Mob Programming)(14:59) The Main Benefit of Ensemble: Single Piece Flow(17:26) How to Do Ensemble and Avoid Common Failure Modes(20:27) The Types of Coding to Ensemble On(22:12) The Importance of Trust, Communication, and Kindness(23:52) Common Things Development Teams Are Struggling With(25:37) Prompt Engineering(27:16) The Samman Method: Learning Hours(29:08) Learning is Part of the Work(31:32) The Practice of Learning as a Team(34:39) The Constraint When Learning from Pull Requests(36:30) Putting Aside Time for Learning Hours(39:14) Becoming a Technical Coach(41:23) How to Measure the Effectiveness of Technical Coaching(43:52) Danger of AI Assisted Coding(46:59) The (Still) Important Skills in the AI Era(49:56) Why We Should Not Refactor Through AI(52:41) The Samman Method & Technical Coaching Resources(53:29) 3 Tech Lead Wisdom(54:56) Finding Mentors for Career Progression_____Emily Bache’s BioEmily Bache is an independent consultant, YouTuber and Technical Coach. She works with developers, training and coaching effective agile practices like Refactoring and Test-Driven Development.Emily has worked with software development for 25 years, written two books and teaches courses on platforms including Pluralsight and O’Reilly. A frequent conference speaker, Emily has been invited to keynote at prestigious developer events including EuroPython, Craft and ACCU. Emily founded the Samman Technical Coaching Society in order to promote technical excellence and support coaches everywhere.Follow Emily:LinkedIn – linkedin.com/in/emilybacheX – x.com/emilybacheMastodon – sw-development-is.social/web/@emilybacheGitHub – github.com/emilybacheWebsite – emilybache.comSamman Coaching – sammancoaching.orgYouTube – youtube.com/@EmilyBache-tech-coachModern Software Engineering – youtube.com/@ModernSoftwareEngineeringYTLike this episode?Show notes & transcript: techleadjournal.dev/episodes/230.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

Why do engineering teams slow down as they scale? It’s not the technology—it’s the management systems.In this episode, Michi Kono, CTO at Garner Health and former engineering leader at Meta, Capital One, and Stripe, shares his battle-tested approach to building scalable engineering organizations. We explore why most teams slow down as they scale and how to build systems that accelerate growth. Our conversation covers everything from designing effective org charts to creating accountability without killing psychological safety. You’ll learn practical strategies for nurturing engineering culture while maintaining high-performance standards.Key topics discussed:The challenges of hypergrowth and the need to constantly reinvent yourselfHow to avoid slowdowns by holding teams accountable for outcomes, not just shipping codeThe art of designing org charts that maximize team autonomyBuilding a culture of accountability and learning from mistakes without blameWhen managers should stop writing code (and why this decision matters)The difference between being a people manager and an executiveWhy communication becomes the most critical skill at senior levelsTimestamps:(00:00) Trailer & Intro(02:10) Career Turning Points(03:55) Skills Advice for Engineers(06:46) The Challenges of a Hypergrowth Company(09:09) Learning and Growing in a Hypergrowth Company(12:07) The Slowdown in Engineering as You Scale(15:55) Designing Organization Structure Well(18:11) Effective Organization Chart Tips(21:05) Nurturing a Good Engineering Culture(25:37) Nurturing Psychological Safety(28:14) Learning from Mistakes & Performance Review(30:27) Being a Mission-Driven Company(32:11) Aligning Mission and Values in the Day-to-Day Work(34:45) The Importance of Management System in Organization(41:53) The Importance of Having Good Managers(45:30) For Strong ICs: Writing Code or Being a Manager?(50:55) The Difference Between a Manager Role and Executive Role(56:01) A Unique Thing Learned from Doing Payment Systems(58:43) 3 Tech Lead Wisdom_____Michi Kono’s BioMichi Kono is the Chief Technology Officer (CTO) at Garner Health, a company on a mission to help people get better healthcare. With a unique and extensive career spanning multiple industries, Michi has navigated the entire spectrum of the tech world. He began his journey in startups, one of which was acquired, leading him to a role at Capital One. From there, he gained invaluable experience at tech giants like Meta and financial-tech leader Stripe before taking the helm at Garner Health. Michi is passionate about the art and science of scaling engineering teams, building resilient cultures, and designing effective management systems to drive success in high-growth environments. He believes deeply in empowering engineers, fostering accountability, and the critical importance of clear communication for any leader.Follow Michi:LinkedIn – linkedin.com/in/michikonoTwitter – x.com/michikonoGarner Health – getgarner.comLike this episode?Show notes & transcript: techleadjournal.dev/episodes/229.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

How do you build a high-performing engineering team in the AI era? And will AI make fundamental engineering skills obsolete?In this episode, Mohan Krishnan, Head of Engineering at Grab, shares lessons from leading multiple transformational engineering teams. Drawing from his experience at Grab, Bukalapak, BBM Emtek, and Pivotal Labs, Mohan explains why core engineering fundamentals still matter, even in the age of AI, and will become even more valuable than ever. He discusses building disciplined, high-performing engineering teams and the importance of hands-on leadership. We also explore the unique challenges and vast potential of the tech landscape in Southeast Asia.Key topics discussed:Why foundational skills like TDD and system design are becoming more critical in the age of generative AIHow to effectively use AI as a pair programmer for upskilling and idea generation, while avoiding the pitfalls of “vibe coding”Mohan’s “sports team” analogy for building successful engineering teams with discipline, a mix of seniority, and a culture of deep learningThe importance of hands-on technical leadership, and why even CTOs should “dive deep” to set the right engineering barThe state of engineering talent in Southeast Asia and what’s needed to bridge the gap in deep tech and AI developmentActionable career advice for junior and mid-career professionals navigating the AI-infused software industryTimestamps:(00:00:00) Trailer & Intro(00:02:08) Career Turning Points(00:06:03) Things We Should Learn in the AI Era(00:09:53) AI as a Pair Programmer(00:13:58) The Danger of Outsourcing Our Thinking to AI(00:17:29) The Dopamine Hit of Using AI(00:20:36) Building a Successful Transformational Engineering Team(00:25:33) The Discipline Rigor in An Engineering Team(00:29:14) Understanding & Delivering Outcomes for the Business(00:32:21) Having a Tough Approach as an Engineering Leader(00:39:07) Going Back as an IC at Google(00:45:40) The Importance of Being Hands-On with Recent Technologies for Leaders(00:52:40) Hands-on vs Micromanagement(00:55:11) Engineering Talents in Southeast Asia(00:58:06) Building Tech Talents in Southeast Asia(01:01:17) Bridging the AI Gap in Southeast Asia(01:04:03) Should We Still Pursue a Tech Career in the AI Era?(01:07:24) 2 Tech Lead Wisdom_____Mohan Krishnan’s BioMohan Krishnan, based in Singapore, is currently a Head of Engineering at Grab. Mohan Krishnan brings experience from previous roles at Google, Bukalapak, BBM and Pt. Kreatif Media Karya. Mohan Krishnan holds a 1998 - 2002 Bachelor of Engineering in Multimedia, Electronics at Multimedia University. With a robust skill set that includes Ruby on Rails, Multithreading, Web Services, HTML, Services and more.Follow Mohan:LinkedIn – linkedin.com/in/mohangkLike this episode?Show notes & transcript: techleadjournal.dev/episodes/228.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

How has Infrastructure as Code changed in the last five years? Explore the key shifts and how to align your infrastructure to real business value.In this episode, Kief Morris, a Distinguished Infrastructure Engineer at Thoughtworks, returns to discuss the third edition of his book “Infrastructure as Code.” He shares fresh insights on designing and delivering dynamic systems for today’s cloud-driven world. Kief explores the evolution of IaC, practical methods for modern teams, the next generation of tools, and lessons learned from the recent years. Learn how to align infrastructure with business needs and manage today’s growing infrastructure complexities.Key topics discussed:How “Infrastructure as Code” book has evolved across three editionsWhy infrastructure decisions must align with business valueHow IaC and the toolchain have evolved over the last few yearsHandling the growing complexity of modern infrastructureThe rise of platform engineering and internal developer platformsTerraform vs. OpenTofu: which one should you use?Balancing governance, speed, and innovation in the cloud eraThe current limitations and role of AI in managing infrastructureTimestamps:(00:00) Trailer & Intro(02:39) Updates in the Last Five Years(04:13) Infrastructure as Code Definition(05:58) The Practice of Infrastructure as Code(06:32) The Differences Between the Book Editions(10:21) Aligning Infrastructure to the Business Value(15:03) Handling the Growing Infrastructure Complexities(19:10) The Tools and New Inventions in IAC(24:11) Terraform vs OpenTofu(27:38) Orchestrating Infrastructure Changes Using IAC(30:35) Platform Engineering(33:06) Internal Developer Platform Key Success Factor(37:15) Key Considerations of Building Teams with Infrastructure Skills(41:56) Infrastructure Compliance and Governance(45:53) Using AI for Infrastructure as Code(50:31) Using AI for Troubleshooting and Root Cause Analysis(51:50) 3 Tech Lead Wisdom_____Kief Morris’s BioKief Morris is the author of the O’Reilly book Infrastructure as Code, and is a Distinguished Infrastructure Engineer at Thoughtworks, based in London. He works with clients and project teams around the world to explore, shape, and share better ways of working with cloud and infrastructure architecture.Kief started out as a developer and systems administrator in the dot-com boom days, then worked with a series of digital scaleups applying infrastructure automation before DevOps was a thing. He joined Thoughtworks in 2010 as the wider industry was discovering Infrastructure as Code, DevOps, and Cloud, which gave him the opportunity to bring what he had learned in the previous fifteen years to enterprise clients in many industries and many countries.He wrote the book Infrastructure as Code (now on the third edition) to share these ideas with a wider audience, which has given him a platform to meet and learn from an ever-growing variety of people and organizations.Follow Kief:LinkedIn – linkedin.com/in/kiefmorrisTwitter – x.com/kiefBlueSky – bsky.app/profile/kief.comPersonal Website – kief.comInfra as Code Website – infrastructure-as-code.com Infrastructure as Code – https://www.oreilly.com/library/view/infrastructure-as-code/9781098150341/Like this episode?Show notes & transcript: techleadjournal.dev/episodes/227.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

Ever wondered how AI is being applied in the world of clinical trials where human lives are at stake?In this episode, Patrick Leung, CTO of Faro Health and former Google Duplex Engineering Lead, reveals how AI is transforming the clinical trial process — a process that can cost up to $2 billion per drug and take over 10 years to complete. Patrick reveals how Faro Health’s AI systems generate complex clinical documentation in minutes instead of months in which hallucinations aren’t acceptable, while navigating the strict regulatory requirements of the healthcare industry.Patrick also reflects on the evolution of AI technologies, the realities of large language models, and offers practical advice on how to thrive in the rapidly changing AI-driven era.Key topics discussed:The evolution of AI from image recognition and Google Duplex to LLMsHow Faro Health uses AI to transform clinical trial processThe challenges of applying AI in highly regulated industriesAI’s potential to save time and millions in clinical trialsHow to tackle AI hallucinations and ensure high-quality outputsPatrick’s thoughts on AGI and the future of AI beyond current capabilitiesThe viability and limitations of vibe codingStrategies and advice for individuals to thrive in the AI eraTimestamps:(00:00) Trailer & Intro(02:09) Career Turning Points(02:46) The Advancements of AI in the Past 10 Years(04:13) Non-LLM Types of AI(05:42) The Google Duplex(07:28) The Use of AI in Faro Health(09:44) Tackling AI Hallucination for Clinical Documents(12:25) Building the Evaluation Process on AI Results(14:28) AI as a Research Assistant(16:40) The Need of Building Custom AI Model(18:50) The Huge Impact of AI in Clinical Trials(21:15) The Regulations on Applying AI Technology(23:28) AI Success Stories in the Life Science Industry(25:16) The Possibility of AGI(28:36) The Path to AGI Using LLM(30:43) Actions People Should Take in the AI Era(35:48) AI Engineers and AI-Enabled Engineers(38:37) The Viability of Vibe Coding(41:03) Hiring AI Engineers(42:26) Important Engineer Attributes in the AI Era(44:23) Important Leader Attributes in the AI Era(46:59) The Room for Juniors in the AI Era(49:04) Inspirational Story of a Successful Junior(51:33) 3 Tech Lead Wisdom_____Patrick Leung’s BioPatrick Leung is a Chief Technology Officer at Faro Health, a company at the forefront of optimizing clinical trial development through the use of artificial intelligence.In his role, he is instrumental in applying large language models and other AI technologies to enhance protocol design and outcomes for clinical trials. A native of New Zealand, Mr. Leung holds degrees in Computer Science and Finance.His career includes being a foundational member of an early e-commerce software company, where he played a key role in guiding the company from its initial stages to a successful initial public offering.Follow Patrick:LinkedIn – linkedin.com/in/puiwahTwitter – x.com/puiwahWebsite – farohealth.comLike this episode?Show notes & transcript: techleadjournal.dev/episodes/226.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

Is your engineering team running like the wild, wild west? What does engineering excellence look like in practice?In this episode, Ganesh Datta, co-founder and CTO of Cortex, explores what it takes to achieve engineering excellence. Ganesh shares lessons from his own journey, from early bug-fixing to building a company focused on engineering excellence.We discuss how platform engineering and internal developer platforms (IDPs) can help teams scale, improve reliability, and align with business outcomes. Ganesh also explains why culture, leadership, and clear metrics matter more than any single tool.If you’re looking to make your engineering team a true business driver, this conversation is for you.Key topics discussed:How to define engineering excellence and why it’s tied to business outcomes.The critical role of leadership in connecting engineering initiatives to business values.When to invest in platform engineering and internal developer platforms as your team grows.Common misconceptions about platform engineering.The importance of clear metrics, shared language, and transparency for continuous improvement.Building a culture that supports operational excellence through rituals and repeated messaging.Real-world examples of using generative AI to accelerate platform adoption and incident analysis.Timestamps:(00:00) Trailer & Intro(01:56) Career Turning Points(07:50) The Practice of Finding the Patterns in Issues(11:39) The Definition of Engineering Excellence(17:10) The Leader’s Role in Engineering Excellence(22:31) Aligning Engineering Excellence with the Business Outcomes(26:30) The Importance of Metrics in Engineering Excellence(33:35) The Culture that Drives Engineering Excellence(39:05) Platform Engineering and Internal Developer Platform(45:02) The Biggest Misconception of Platform Engineering or IDP(50:36) Cortex as an Engineering Excellence Platform(52:39) Generative AI Use Case in Platform Engineering(55:26) 3 Tech Lead Wisdom_____Ganesh Datta’s BioGanesh Datta is a Co-Founder & CTO of Cortex. Before co-founding Cortex, he was a Principal Software Engineer at Mission Lane where he was responsible for driving the development of real-time underwriting infrastructure. At LendUp, Ganesh was a Senior Software Engineer leading the development and optimization of the company’s decisioning infrastructure and financial account management system. Ganesh holds a bachelor of science in computer science from the University of California San Diego.Follow Ganesh:LinkedIn – linkedin.com/in/gsdattaTwitter – x.com/gsdattaWebsite – www.cortex.ioEmail – ganesh@cortex.ioJoin Ganesh & Cortex at IDPCon in NYC – ipdcon.comLike this episode?Show notes & transcript: techleadjournal.dev/episodes/225.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

Is your software development process stuck on a conveyor belt? Discover how to break free from outdated manufacturing mindsets and build truly high-performing, agile teams that “Move Fast and Break Silos.”In this episode, experienced CPTO, Klaus Breyer, introduces a revolutionary approach to software development. He explains why treating software engineering like a factory assembly line leads to inefficiency, micromanagement, and disempowered teams. Learn how to slice work effectively—from objectives down to delivery—and align small, empowered teams to solve real customer problems and ship value faster.Key topics discussed:Why software development is a design process instead of a manufacturing processHow Agile and Scrum has become micromanagement toolsWhy ticketing systems can create communication silosHow to slice work into objectives, problems, solutions, and deliveryGiving teams problems to solve, not just solutions to buildThe concept of empowered teams that own their outcomesWhy small, dynamic groups of 2-3 people work bestAligning your teams’ work with company goals and business objectives Timestamps:(00:00) Trailer & Intro(02:10) Career Turning Points(05:26) Critical Key Skills as CPTO(07:40) Juggling Between Being Optimistic vs Pessimistic(09:15) Move Fast and Break Silos(13:08) The Difference Between Manufacturing and Software Development(16:51) The Problems with the Status Quo of Software Development Practices(23:50) Key Practice 1: Slicing Work(25:51) Slicing Objectives(28:30) Slicing Problems(33:25) Slicing Solutions(38:03) Slicing Delivery(41:09) Key Practice 2: Aligning Teams(43:21) The Effective Teams Alignment Practices(48:10) Working in Small Teams at a Time(51:07) Alignment with the Value Streams(53:15) Mapping the Sliced Work to the Organization(56:41) The Importance of Reporting Structure in the Large Organization(58:52) 3 Tech Lead Wisdom_____Klaus Breyer’s BioKlaus Breyer is an experienced B2B SaaS CPTO who specializes in bridging the gap between technical delivery and agile product strategy, driven by a passion for breaking down silos. His career includes founding and leading the startups Buddybrand (a digital agency) and BuzzBird (a B2B marketplace), as well as building corporate startups and business units for major companies like Voith and edding in the IoT and B2B SaaS sectors.Based in Berlin, he has extensive experience working with diverse and primarily remote teams. In addition to his leadership roles, he sometimes invests in and advises leadership teams on building effective interdisciplinary teams themselves. He is also a speaker, blogger, and book author who champions the philosophy of “Move Fast And Break Silos!”Follow Klaus:LinkedIn – linkedin.com/in/klaus-breyerTwitter – twitter.com/klausbreyerWebsite – v01.ioEmail – kb@v01.ioLike this episode?Show notes & transcript: techleadjournal.dev/episodes/224.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

Is AI taking over the craft of coding? Many engineers now face an identity crisis.In the episode, Distinguished Engineer Annie Vella discusses her research on AI’s impact on software development. She explores the “software engineering identity crisis” as the craft of coding becomes automated. Annie warns that the seductive speed of AI tools can lead to lower quality and delivery instability, a trend supported by reports from DORA and GitClear. She also cautions that over-reliance on AI prevents engineers from gaining the hands-on experience needed for deep skill acquisition.Key topics discussed:How AI is reshaping the software development lifecycleThe software engineer’s professional identity crisisThe real danger of over-relying on AI toolsHow to balance the seduction of speed with long-term qualityCrucial advice for junior engineers entering the industryWhy leaders must shift focus from speed to qualityThe idea of treating AI as a team member instead of just a tool  Timestamps:(00:00:00) Trailer & Intro(00:02:32) AI Impact on Career and Software Engineering(00:07:00) The Future of AI-Driven Software Engineering(00:14:29) The Shift in the Role of Software Engineer(00:22:13) When Writing Code is Not the Bottleneck Anymore(00:32:04) The Danger of Over-Reliance on AI(00:38:51) The Software Engineering Identity Crisis(00:48:09) Advice for Junior Engineers in This Challenging Time(00:53:34) The Shift in the Role of Engineering Management(00:59:46) You Are Not Alone(01:00:50) 3 Tech Lead Wisdom_____Annie Vella’s BioAnnie Vella is a Distinguished Engineer at Westpac NZ with two decades of experience in software engineering and technical leadership across various industries and countries.Vella has returned to an engineering role after a period in management and is also a part-time Master’s student at the University of Auckland, researching the impact of AI on software engineering. She believes that technologies like Generative AI, LLMs, and Agentic AI will revolutionize the field and problem-solving in general.Follow Annie:LinkedIn – linkedin.com/in/annievellaX – x.com/codefrenzyWebsite – annievella.com/Like this episode?Show notes & transcript: techleadjournal.dev/episodes/223.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

What if your most critical systems run on code that no one fully understands?In this episode, Omer Rosenbaum, CTO and co-founder of Swimm, explains how to use AI to close the knowledge gap in your legacy codebase. Discover the limitations of AI in understanding legacy code and learn novel approaches to automatically document complex systems, ensuring their critical business logic is preserved and understood within the organization. Beyond legacy systems, Omer also shares practical advice for how junior developers can thrive in the AI era and how teams and organizations can conduct more effective research.Key topics discussed:How junior developers can thrive in the age of AIThe danger of shipping code you don’t fully understandWhy AI can’t deduce everything from your code aloneHow writing documentation becomes more critical now with AIHow to analyze code that even LLMs struggle to read, like COBOLHow to keep your organization’s knowledge base trustworthy and up to dateThe real danger of letting AI agents run uncheckedA practical approach to conducting more effective research  Timestamps:(00:00) Trailer & Intro(02:10) Career Turning Points(05:24) What Juniors Should Do in the Age of AI(11:05) Junior Developer’s Responsbility When Using AI(14:50) AI and Critical Thinking(16:20) Understanding & Preserving Domain Knowledge(18:11) The Importance of Written Knowledge for AI Usage(21:51) Limitations of AI in Understanding Knowledge Base(26:34) The Limitations of LLM in Navigating Legacy Codebases (e.g. COBOL)(32:38) Effective Knowledge Sharing Culture in the Age of AI(34:54) Keeping Knowledge Base Up-to-Date(36:55) Keeping the Organization Knowledge Base Accurate(39:08) Fact Checking and Preventing AI Hallucination(41:24) The Potential of MCP(43:24) The Danger of AI Agents Hallucinating with Each Other(45:00) How to Get Better at Research(53:41) The Importance of Investing in Research(57:18) 3 Tech Lead Wisdom_____Omer Rosenbaum’s BioOmer Rosenbaum is the CTO and co-founder of Swimm, a platform reinventing the way engineering organizations manage internal knowledge about their code base. Omer founded the Check Point Security Academy and was the Cyber Security Lead at ITC, an educational organization that trains talented professionals to develop careers in technology. Omer has a MA in Linguistics from Tel Aviv University and is the creator behind the Brief YouTube Channel.Follow Omer:LinkedIn – linkedin.com/in/omer-rosenbaum-034a08b9Twitter – x.com/Omer_RosSwimm – swimm.ioEmail – omer@swimm.io📚 Gitting Things Done – buymeacoffee.com/omerr/extras▶️ Brief – youtube.com/@BriefVidLike this episode?Show notes & transcript: techleadjournal.dev/episodes/222.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

Feeling like you have valuable technical insights to share but struggle to put them into words? You’re not alone.In this episode, Piotr Sarna, author of “Writing for Developers” and an experienced open-source maintainer, shares the common hurdles developers face in writing and provides practical tips to get started. Discover how cultivating a writing habit can not only boost your personal brand but also improve your technical skills and create new career opportunities.Key topics discussed:The Writing Challenge: Why many developers who have interesting things to say don’t write and the importance of writing culture in a company.Finding Your First Topic: How to identify valuable topics from your daily work, even if you think they’re not interesting enough or have already been written about.Overcoming Writer’s Block: Practical tips to overcome the fear of writing, including dealing with imposter syndrome and language concerns.Leveraging AI for Writing: How to effectively use AI as a reviewer to find logical fallacies, get feedback, and improve your writing without sacrificing authenticity.Proven Blog Post Patterns: Learn about effective patterns like the “Bug Hunt” to create engaging and educational content.Promoting Your Writing: Strategies to get your work in front of a larger audience, from company blogs to social media and content aggregators.Beyond the Blog Post: Discover how writing can open doors to speaking at conferences and even writing a book.  Timestamps:(00:00) Trailer & Intro(02:06) Career Turning Points(04:30) The Challenge of Writing for Developers(06:08) The Importance of Writing Culture(08:36) Piotr’s Journey to Writing Books(11:19) The Impact of Writing on Engineering Culture(13:39) How to Overcome Common Excuses for Not Writing(16:32) Finding The First Blog Post Topic(20:32) Tips on How to Start Writing(22:19) The Importance of Goal and Perspective in Writing a Draft(24:55) The Use of AI in Writing(29:01) AI Prompts to Improve Your Writing(30:14) The Best LLM Model for Writing(31:53) The Best Workflow Working with AI(33:41) Blog Post Pattern: Bug Hunt(37:16) Blog Post Pattern: Thoughts on Trends(40:13) The Importance of Promoting Our Writing(42:47) How to Promote Your Writing Independently(45:00) Future Opportunities of Writing(47:55) Writing as a Developer(49:02) 3 Tech Lead Wisdom_____Piotr Sarna’s BioPiotr Sarna is a software engineer who is keen on open source projects and the Rust and C++ languages. He previously developed an open source distributed file system and had a brief adventure with the Linux kernel. He’s also a long-time contributor and maintainer of ScyllaDB, as well as libSQL and Turso. Piotr graduated from University of Warsaw with a Master’s degree in computer science.Follow Piotr:LinkedIn – linkedin.com/in/sarna-devTwitter – x.com/sarna_devGitHub – github.com/psarnaWebsite – bio.sarna.devWrite That Blog! – writethat.blogInterview with Tech Bloggers – writethatblog.substack.com📚 Writing for Developers – https://www.manning.com/books/writing-for-developersLike this episode?Show notes & transcript: techleadjournal.dev/episodes/221.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

In this special in-person episode, Sanne Grinovero shares the story of Java’s evolution from his unique perspective as a long-time open-source contributor. He shares his 16-year career journey at Red Hat, highlighting his amazing work on key projects like Hibernate, Infinispan, and especially the creation of Quarkus. His career trajectory, from a student who initially disliked Java’s complexity to a leading figure in its modernization, shows the transformative power of open source.A key part of the conversation focuses on how technical challenges spark innovation. Sanne explains how the task of making the popular Hibernate framework compatible with GraalVM’s limitations led directly to the birth of Quarkus. This journey tells the bigger story of how Java adapted for cloud-native development, ensuring it continues to be a top choice for developers seeking high performance and a great developer experience.  Timestamps:(00:00:00) Trailer & Intro(00:02:16) Career Turning Points(00:04:52) Winning an Innovation Award(00:06:35) Java Heroes(00:08:04) Working as a Consultant(00:09:56) Taking a Massive Pay Cut to Work on Open Source(00:10:59) Contributing to Big Open Source as a Youngster(00:12:53) State of Hibernate Project(00:15:15) Spring Boot(00:16:54) Making Hibernate Work on GraalVM(00:21:05) GraalVM Limitations for Running Hibernate(00:26:09) Java for Cloud Native Application(00:28:04) Quarkus vs Spring Boot(00:33:21) JRebel & Quarkus(00:34:35) Java vs New Programming Languages(00:39:22) The ORM Dilemma(00:42:38) Some Hibernate Design Pattern Tips(00:46:40) Getting Paid Working on Open Source(00:48:41) Hibernate License Change(00:51:05) Intellectual Property & Meaningful Contributions(00:52:52) AI Usage & Copyright in Open Source(00:55:21) Biggest Challenge Working in a Big Open Source(00:56:08) Politics in Open Source(00:58:32) Security Risks in Open Source(01:02:25) Donating Hibernate to Commonhaus Foundation(01:04:49) The Future of Red Hat(01:06:39) 3 Tech Lead Wisdom_____Sanne Grinovero’s BioSanne Grinovero has been a member of the Hibernate team for 10 years; today he leads this project in his role of Sr. Principal Software Engineer at Red Hat, while also working on Quarkus as a founding R&D engineer.Deeply interested in solving performance and concurrency challenges around data access, scalability, and exploring integration with new storage technologies, distributed systems and search engines.Working on Hibernate features led him to contribute to related open source technologies; most notably to Apache Lucene and Elasticsearch, Infinispan and JGroups, ANTLR, WildFly, various JDBC drivers, the OpenJDK and more recently getting interested in GraalVM.After being challenged to reduce memory consumption and improve bootstrap times of Hibernate, Sanne worked as part of a small R&D team at Red Hat on some ideas which have evolved into what is known today as Quarkus.Follow Sanne:LinkedIn – linkedin.com/in/sannegrinoveroTwitter – twitter.com/SanneGrinoveroGitHub – github.com/sanneLike this episode?Show notes & transcript: techleadjournal.dev/episodes/220.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

Tired of feeling like your team is stuck in a cycle of frustration and miscommunication? What if the biggest blocker in your tech career isn’t your code, but your thinking?That’s the core premise of Systems Thinking, and in this episode, Diana Montalion (author of “Learning Systems Thinking”) shares the practical insights and mental models to help you make that essential shift.Key topics discussed:What systems thinking is and its core principlesThe difference between linear thinking (which we need) and systems thinking (which we’re missing)Why building a metaphorical “car boat” is a failure of “conceptual integrity” and how to avoid itHow to break free from a “change-my-mind” culture and improve our collaborationThe critical skill of metacognition: why you must understand your own thinking before you can influence othersPractical ways to foster collective systems thinking and bridge the gap between Product and TechUsing modeling and visual tools to create alignment and solve the right problemsHow AI’s inability to handle true inference makes human systems thinking more valuable than everWhether you’re a software engineer, architect, team leader, or anyone tackling complex problems, learn why your technical skills alone are not enough and how a shift in your thinking can revolutionize your work and career.  Timestamps:(00:00:00) Trailer & Intro(00:02:23) Career Turning Points(00:04:35) Writing Learning Systems Thinking(00:08:53) Definition of Systems Thinking(00:13:39) Systems Thinking vs Linear Thinking(00:19:31) Definition of System(O0:24:13) Conceptual Integrity(00:30:02) Practices to Improve Our Systems Thinking(00:36:21) Metacognition and Self-Awareness(00:44:42) Practices to Improve Our Collective Systems Thinking(00:53:04) Collaboration with Consent(00:55:29) The Importance of Modeling(01:02:20) AI Usage and System Thinking(01:11:04) 3 Tech Lead Wisdom_____Diana Montalion’s BioDiana Montalion is a systems architect, learning facilitator, and founder of Mentrix Group, with over 20 years of experience delivering transformative software initiatives for organizations like Stanford, The Gates Foundation, The Economist, and The Wikimedia Foundation. As the author of Learning Systems Thinking: Essential Nonlinear Skills & Practices for Software Professionals (O’Reilly), she empowers tech professionals to navigate complex systems through practices like systemic reasoning, metacognition, and collaborative modeling.Follow Diana:LinkedIn – linkedin.com/in/dianamontalionWebsite – montalion.comTwitter – @dianamontalionMastodon - @diana@hachyderm.ioBluesky - @mentrix.bsky.socialMentrix Group – https://mentrixgroup.com/SystemCrafters Collective – https://mentrix.systems/📚 Learning Systems Thinking – oreilly.com/library/view/learning-systems-thinking/9781098151324/Our SponsorsManning Publications is a premier publisher of technical books on computer and software development topics for both experienced developers and new learners alike. Manning prides itself on being independently owned and operated, and for paving the way for innovative initiatives, such as early access book content and protection-free PDF formats that are now industry standard.Get a 40% discount for Tech Lead Journal listeners by using the code techlead24 for all products in all formats.Like this episode?Show notes & transcript: techleadjournal.dev/episodes/219.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

Understand the secret behind one of Amazon’s most powerful innovation tools and learn how you can use it to drive clarity, alignment, and better decision-making.In this episode, Marcelo Calbucci, author of “The PRFAQ Framework,” dives deep into the PRFAQ (Press Release & Frequently Asked Questions) framework, a unique approach that combines narrative storytelling and strategic FAQs to crystallize initiative vision and strategy.Key topics discussed:What the PRFAQ framework is — and why it’s more than just a product management toolHow PRFAQ brings Amazon’s “working backwards” philosophy to lifeThe structure of a PRFAQ: press release, customer FAQs, and internal FAQsWhy storytelling and precise writing are essential for strategic vision and alignmentOvercoming resistance: making writing and reading strategic documents part of your culturePractical tips for adopting PRFAQ in any organization, large or smallCommon mistakes to avoid when implementing PRFAQThe importance of collaborative feedback in the PRFAQ processWhether you’re launching a startup, building a new product, or transforming internal processes, this episode breaks down how this method can help you avoid common pitfalls and deliver results that matter.Timestamps:(00:00) Trailer & Intro(02:10) Career Turning Points(03:56) The PRFAQ Framework(05:19) PRFAQ is Forward-Looking(07:09) Working Backwards & PRFAQ(07:58) Why Writing a Book About PRFAQ(11:37) PRFAQ: Why Less Adoption Than Other Frameworks?(14:40) Writing PRFAQ vs Speed of Execution(16:28) The PRFAQ Template(19:05) The Six Page of PRFAQ(21:24) Precise Writing(25:09) The Strict Guidelines of PRFAQ(26:40) PRFAQ: Press Release(29:56) The Power of Narratives / Storytelling(32:03) PRFAQ: Customer FAQ(34:15) Jobs-to-Be-Done vs. Personas(36:46) PRFAQ: Internal FAQ(39:34) How to Come Up with the Internal FAQs(40:49) The Level of Details in the FAQs(43:20) PRFAQ: Appendix(45:27) Advice on Starting PRFAQ(46:11) Adapting from the Amazon’s PRFAQ(48:55) Common Mistakes when Adopting PRFAQ(50:05) Providing Good Feedback for PRFAQ(51:18) 3 Tech Lead Wisdom_____Marcelo Calbucci’s BioMarcelo Calbucci is an entrepreneur, innovator, and technologist. He’s been building software products for over thirty years, having sold his first software at age fourteen. He has worked at Microsoft (Exchange Server & Bing) and Amazon (People eXperience & Technology), leading software engineering, product, data science, and UX. He is an author of The PRFAQ Framework.Follow Marcelo Calbucci:LinkedIn – linkedin.com/in/marcelocalbucciTwitter / X – @calbucciEmail – marcelo@theprfaq.com📚 The PRFAQ Framework – theprfaq.comOur SponsorsManning Publications is a premier publisher of technical books on computer and software development topics for both experienced developers and new learners alike. Manning prides itself on being independently owned and operated, and for paving the way for innovative initiatives, such as early access book content and protection-free PDF formats that are now industry standard.Get a 40% discount for Tech Lead Journal listeners by using the code techlead24 for all products in all formats.Like this episode?Show notes & transcript: techleadjournal.dev/episodes/218.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

(08:54) Brought to you by Swimm.io.⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Start modernizing your mainframe faster with ⁠⁠⁠Swimm⁠⁠⁠. Understand the what, why, and how of your mainframe code. Use AI to uncover critical code insights for seamless migration, refactoring, or system replacement.Why do so many well-intentioned initiatives fail to move the needle?In this episode, Sriram Narayan, author of ‘Impact Intelligence,’ reveals how to ensure your efforts translate into real, measurable business impact. Stop shooting in the dark and start delivering tangible results that matter.Key topics discussed:What “Impact Intelligence” means and why it is crucial for any businessThe common pitfalls: Why many tech and digital initiatives fail to achieve their intended business impactThe common misconceptions about “outcomes” in tech and product teams, and why delivery or adoption metrics are not enoughSurprising insights from the non-profit sector on rigorous impact measurement practicesUnderstanding the difference between immediate (proximate) results and long-term (downstream) impactHow to visualize and map your initiatives to core business goals using an “Impact Network”The critical challenge of “Impact Attribution” – how to know if your project actually moved the needleAddressing “Measurement Debt” — if you can’t measure it, should you build it?The iRex framework: A modular approach to building your organization’s Impact IntelligenceBalancing speed vs impact: Not just shipping features, but delivering measurable business resultsWhether you’re a tech leader, product manager, or executive, this episode will equip you with actionable frameworks and real-world examples to focus on what really matters: delivering measurable, meaningful business impact.Tune in and start building your organization’s Impact Intelligence muscle today!  Timestamps:(00:00) Trailer & Intro(02:22) Career Turning Points(10:52) Impact Intelligence(11:40) The Importance of Impact Intelligence(15:09) Understanding Business Impact(19:11) Learning & Adopting from the NGO Space(22:35) Impact Feedback Loops(26:25) Proximate vs Downstream Impact(28:20) Building an Impact Network(36:47) Differences with OKR(38:12) Impact Attribution(44:51) The Importance of Measurement & Measurement Debt(48:31) iRex Framework(54:26) Balancing Between Speed of Delivery and Business Impact(57:32) 1 Tech lead Wisdom_____Sriram Narayan’s BioSriram Narayan is an independent consultant in the area of impact intelligence. He also helps clients improve digital, product and tech performance.Pearson published his first book, Agile IT Org Design , in 2015. It won endorsements from the then CIO of The Vanguard Group and the then MD of Consumer Digital at Lloyds Bank.Sriram has served in product, technology, innovation, and transformation leadership roles since 2006. He has also helped some of his clients move to a product operating model. His write-up of the topic in 2018 has since become a de facto industry reference. His other writings and talks are available at agileorgdesign.comFollow Sriram:LinkedIn – linkedin.com/in/mrsriramnarayanBluesky - @srny.bsky.socialTwitter / X – @sriramnarayan📚 Impact Intelligence Website – impactintel.net📚 Agile Org Design Website – agileorgdesign.comEmail – sriram@agileorgdesign.comOur SponsorsManning Publications is a premier publisher of technical books on computer and software development topics for both experienced developers and new learners alike. Manning prides itself on being independently owned and operated, and for paving the way for innovative initiatives, such as early access book content and protection-free PDF formats that are now industry standard.Get a 40% discount for Tech Lead Journal listeners by using the code techlead24 for all products in all formats.Like this episode?Show notes & transcript: techleadjournal.dev/episodes/217.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

(05:46) Brought to you by Swimm.io.⁠⁠⁠⁠⁠⁠⁠⁠Start modernizing your mainframe faster with ⁠⁠Swimm⁠⁠.Understand the what, why, and how of your mainframe code.Use AI to uncover critical code insights for seamless migration, refactoring, or system replacement.Feeling uneasy about how your personal data is used, and wondering if companies are doing enough to protect it?In this episode, Katharine Jarmul, author of “Practical Data Privacy,” dives deep into one of the most critical and rapidly evolving topics today. Discover how data privacy impacts you as a user and what organizations should be doing to protect your information responsibly. Learn why simply blaming users isn’t the answer and how we can build a more trustworthy technological future.Key topics discussed:Understanding Data Privacy: The meaning of data privacy and how it links to autonomy, trust, and choiceMore Than Just PII: The full scope of sensitive data needing protectionThe “Spying” Phone Feeling: How too much data collection can be used to infer sensitive detailsOrganizational Responsibility: Shifting data protection burden from users to companies building and deploying technologyPrivacy by Design: Embedding privacy into tech right from the startEssential Data Governance: Why knowing your data is key to privacyPractical Privacy Techniques: Pseudonymization, anonymization, data masking, and morePrivacy Enhancing Technologies: Exploring tools like differential privacy, federated learning, and encrypted computationAI & Privacy Challenges: Using AI responsibly with sensitive informationNavigating Privacy Laws: Understanding GDPR, data sovereignty, and global regulationsBuilding a Privacy Culture: Fostering a culture of learning, psychological safety, and risk awareness around privacyTune in to learn how we can build a safer, more responsible, and trustworthy digital future for everyone.  Timestamps:(00:00) Trailer & Intro(01:20) Career Turning Points(02:14) Data Privacy Landscape(07:45) PII (Personally Identifiable Information)(11:33) Data Privacy Risk in Current Technologies(14:13) Data Utility vs Privacy(19:01) Privacy by Design(24:19) Data Governance(29:06) Retention Schedule(31:10) Data Privacy Practices & Techniques(34:09) Privacy Enhancing Technologies(38:52) Fostering Data Privacy Practice & Culture(47:05) The Legal Aspects of Data Privacy(51:10) AI and Data Privacy(56:08) 3 Tech Lead Wisdom_____Katharine Jarmul’s BioKatharine Jarmul is a Principal Data Scientist at Thoughtworks Germany and author of the recent O’Reilly book Practical Data Privacy . Previously, she has held numerous roles at large companies and startups in the US and Germany, implementing data processing and machine learning systems with a focus on reliability, testability, privacy and security.She is a passionate and internationally recognized data scientist, programmer, and lecturer. Katharine is also a frequent keynote speaker at international software and AI conferences.Follow Katharine:LinkedIn – linkedin.com/in/katharinejarmulNewsletter – https://probablyprivate.comYouTube – @ProbablyPrivate📚 Practical Data Privacy: Enhancing Privacy and Security in Data – https://www.oreilly.com/library/view/practical-data-privacy/9781098129453/Our SponsorsManning Publications is a premier publisher of technical books on computer and software development topics for both experienced developers and new learners alike. Manning prides itself on being independently owned and operated, and for paving the way for innovative initiatives, such as early access book content and protection-free PDF formats that are now industry standard.Get a 40% discount for Tech Lead Journal listeners by using the code techlead24 for all products in all formats.Like this episode?Show notes & transcript: techleadjournal.dev/episodes/216.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

(04:07) Brought to you by Swimm.io.⁠⁠⁠⁠⁠⁠Start modernizing your mainframe faster with ⁠Swimm⁠.Understand the what, why, and how of your mainframe code.Use AI to uncover critical code insights for seamless migration, refactoring, or system replacement.Are too many meetings killing your productivity and making your team less effective?Discover a new approach to work where meetings are no longer the default and deep work takes the center stage.In this episode, Sumeet Moghe, the author of the “Async-First Playbook”, shares actionable insights on building high-performing teams through async-first approach.Key topics discussed:The real reasons behind the return-to-office trend, and why remote and async work are far from deadHow async-first companies like GitLab, Shopify, and Automattic operate, and why it’s not an all-or-nothing approachSurprising survey findings: Why most people want to work remotely, and how meetings and interruptions are damaging productivityThe async-first mindset: Making meetings the last resort, prioritizing written communication, and defining reasonable response lagsThe ConveRel Quadrants: A framework for deciding when to meet based on relationship strength and meeting purposeInclusion as a first-class responsibility: How async work empowers introverts, non-native speakers, parents, and diverse team membersThe “default to action” principle: How teams can move faster by embracing reversible decisions and reducing bottlenecksAsync-first leadership: Building trust, modeling the right behaviors, and creating systems that replace performative busynessPractical tips for better business writing and reading, plus how AI tools can supercharge your communicationThe future of work: Why top talent will continue to demand autonomy, and how AI and fractional work are shaping new collaboration modelsTune in to discover how to build high-performing, effective and inclusive teams with fewer meetings by adopting async-first.  Timestamps:(00:00) Trailer & Intro(02:19) Career Turning Points(06:21) The Return to Office Trend(11:36) Companies Embracing Async-First(13:20) People’s Working Style Preference(17:37) What is Async-First?(21:39) Team Handbook and Ways of Working(23:24) The ConveRel Quadrants(27:41) Inclusion as a First-Class Responsibility(32:14) Defaulting to Action(35:50) Async-First Leadership(40:38) Being Good in Written Communication(44:35) AI Usage in Written Communication(46:17) Time to Read and Reading Comprehension(51:14) The Future of Work(58:33) 3 Tech Lead Wisdom_____Sumeet Moghe’s BioSumeet Gayathri Moghe is an Agile enthusiast, product manager, and design nerd at Thoughtworks. Sumeet has recently authored The Async-First Playbook. His practical recommendations for effective collaboration within remote and distributed teams stand for what he’s learned from his colleagues, their successes, and their occasional misadventures.Sumeet kicked off “The async-first manifesto” , a set of principles he is co-creating with volunteer enthusiasts from around the world. He is also bringing async-work to life with stories of “Humans of remote work” .Follow Sumeet:LinkedIn – linkedin.com/in/sumeetmogheWebsite – asyncagile.org📚 Async-First Playbook – https://informit.com/asyncUse the code "MOGHE" to get 35% offOur SponsorsManning Publications is a premier publisher of technical books on computer and software development topics for both experienced developers and new learners alike. Manning prides itself on being independently owned and operated, and for paving the way for innovative initiatives, such as early access book content and protection-free PDF formats that are now industry standard.Get a 40% discount for Tech Lead Journal listeners by using the code techlead24 for all products in all formats.Like this episode?Show notes & transcript: techleadjournal.dev/episodes/215.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

(03:59) Brought to you by Swimm.io.⁠⁠⁠⁠Start modernizing your mainframe faster with Swimm.Understand the what, why, and how of your mainframe code.Use AI to uncover critical code insights for seamless migration, refactoring, or system replacement.Stop fearing Friday and late-night deployments!Discover how the most painful part of software development—deploying to production—can become routine, safe, and even boring.In this episode, I sit down with Valentina Servile (ThoughtWorks lead developer and author of “Continuous Deployment”) to discuss the principles, practices, and mindset shift required to achieve true Continuous Deployment.Key topics discussed:The key differences between Continuous Integration, Continuous Delivery, and Continuous DeploymentWhy “if it hurts, do it more often” is the secret to safer, faster releasesApplying Lean principles like one-piece flow and reducing batch size for higher quality and speedThe importance of removing the final manual deployment gate and automating everythingEssential minimum practices: robust automated testing, feature flags, static analysis, and zero-downtime deploymentsSeparating deployment from release with feature flags and expand/contract patternsOvercoming challenges in regulated industries, technical hurdles, and third-party integrationsThe critical mindset shift: treating production as a first-class citizen and embracing “shift left” for quality and securityCautions and advice on using AI tools in a continuous deployment workflowTune in to level up your software delivery and learn how to make deployments so routine that you’ll never dread another release.  Timestamps:(02:00) Career Turning Points(06:05) Tips for Juniors Starting Their Careers(08:00) Continuous Deployment Book(10:16) Definitions of CI, CD, Continuous Deployment(15:42) If It Hurts, Do It More Often(19:18) Why Remove The Final Manual Gate to Production(24:56) Common Challenges in Adopting Continuous Deployment(30:02) Minimum Practices for Continuous Deployment(35:17) Hiding Work-in-Progress(38:46) The Difference Between Deployment vs Release(41:40) Slicing the Work(45:10) Coordinating Changes Between Systems & Third Parties(47:58) The Importance of Backward Compatibility(50:05) The Required Mindset Shift(53:16) AI Caution in Continuous Deployment(55:35) 3 Tech Lead Wisdom_____Valentina Servile’s BioValentina Servile is a full-stack software craftswoman and Lead Software Developer at Thoughtworks.She has worked with over a dozen companies in 5 different countries, ranging from start-up to enterprise scale. Her work has been focused on clean code, distributed systems and microservices, CI/CD practices, and evolutionary architectures in a variety of tech stacks. As a technical lead, she also coordinates delivery, and ensures a shared vision around ways of working and technical health in her cross-functional teams.Valentina is passionate about creating an engineering baseline of clean code, testing and automation as the the most fundamental enabler of Agile, Lean and DevOps principles.Follow Valentina:LinkedIn – linkedin.com/in/valentina-servileBluesky – @valentinaservile.bsky.social📚 Continuous Deployment – https://www.oreilly.com/library/view/continuous-deployment/9781098146719/Our SponsorsManning Publications is a premier publisher of technical books on computer and software development topics for both experienced developers and new learners alike. Manning prides itself on being independently owned and operated, and for paving the way for innovative initiatives, such as early access book content and protection-free PDF formats that are now industry standard.Get a 40% discount for Tech Lead Journal listeners by using the code techlead24 for all products in all formats.Like this episode?Show notes & transcript: techleadjournal.dev/episodes/214.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

(05:57) Brought to you by Swimm.io.⁠⁠⁠⁠Start modernizing your mainframe faster with Swimm.Understand the what, why, and how of your mainframe code.Use AI to uncover critical code insights for seamless migration, refactoring, or system replacement.Are we looking at software engineering the wrong way?What if it’s less about writing code and more about making better decisions in an ever-changing system?Learn a revolutionary approach to understanding complex software systems in my conversation with Tudor Girba, the CEO of feenk. We explore “Moldable Development,” a groundbreaking concept that challenges traditional views of software engineering. Learn why treating development as a decision-making process, supported by custom tools, is crucial for tackling today’s software challenges, especially when dealing with legacy systems.Key topics discussed:Software Engineering as Decision-Making: Why software development is fundamentally about making informed decisions rather than just constructing systems.The Inefficiency of Reading Code: Developers spend over 50% of their time reading code, yet this activity remains unoptimized.Moldable Development: Learn how creating custom tools tailored to specific problems can revolutionize your workflow and decision-making process.Legacy Systems as Opportunities: Reframe legacy systems as value-creation opportunities instead of burdens.Glamorous Toolkit: Discover the innovative development environment enabling thousands of micro-tools for better system understanding.The Future of Development Environments: Explore how AI, moldable development, and tools like Glamorous Toolkit can coexist to solve diverse class of problems.This conversation will completely transform how you think about software development!  Timestamps:(00:01:57) Career Turning Points(00:08:29) Understanding How We Read Code(00:10:43) Software Engineering is a Decision-Making Activity(00:13:19) Reading Code is a Suboptimal Activity(00:16:44) Moldable Development(00:22:47) The Challenges with Legacy Systems(00:30:17) Moldable Development Workflow(00:46:02) Glamorous Toolkit(00:54:15) IDE, AI, and Glamorous Toolkit(01:00:36) Writing with Simon Wardley(01:03:01) 1 Tech Lead Wisdom_____Tudor Girba’s BioTudor Girba is the CEO of feenk, a company focused on modernizing legacy systems. They do that through Moldable Development, a way of programming through contextual tools. They build Glamorous Toolkit, a free and open-source moldable development environment, to show how working through thousands of contextual tools per system can be practical. In 2014, Tudor received the prestigious Dahl-Nygaard Junior Prize for his work on modeling and visualisation of evolution and interplay of large numbers of objects.Follow Tudor:LinkedIn – linkedin.com/in/girbaBluesky – bsky.app/profile/tudorgirba.comX – x.com/girbafeenk – feenk.comGlamorous Toolkit – gtoolkit.com📝 Rewilding Software Engineering – medium.com/feenk/rewilding-software-engineering-900ca95ebc8c_____Our SponsorsManning Publications is a premier publisher of technical books on computer and software development topics for both experienced developers and new learners alike. Manning prides itself on being independently owned and operated, and for paving the way for innovative initiatives, such as early access book content and protection-free PDF formats that are now industry standard.Get a 40% discount for Tech Lead Journal listeners by using the code techlead24 for all products in all formats.Like this episode?Show notes & transcript: techleadjournal.dev/episodes/213.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

(07:40) Brought to you by Swimm.io.⁠⁠⁠⁠Start modernizing your mainframe faster with Swimm.Understand the what, why, and how of your mainframe code.Use AI to uncover critical code insights for seamless migration, refactoring, or system replacement.What if everything you’ve been taught about software architecture is fundamentally at odds with how the real world works?Dive into my conversation with Barry O’Reilly, a veteran architect and former Chief Architect at Microsoft, as we explore a radical rethinking of software architecture that embraces uncertainty and complexity. Discover how to design systems that survive in an ever-changing world.Key topics discussed:The Architect’s Paradox: Why rigid logic fails when applied to human systems and business complexity.The Failures of Traditional Architecture: Why requirements engineering and rigid models often fall short.Residuality Theory: A revolutionary approach focused on how systems collapse and adapt over time.Correctness vs. Criticality: Designing architectures that survive off-spec scenarios rather than aiming for perfection.Philosophy in Architecture: Unpacking hidden “default” philosophies that shape how we build software–and why they need to change.Essential Mindset for Architects: Humility, pessimism, and embracing uncertainty as tools for success.  Whether you’re a developer, architect, or business stakeholder, this episode will challenge your assumptions and inspire new ways of thinking about software architecture.Timestamps:(02:00) Career Turning Points(10:02) The Architect’s Paradox(15:54) Barry’s Definition of Architecture(20:24) The Challenges of Time and Change(24:09) The Danger of Software Abstractions(29:41) Understanding Our Architecture Philosophy(37:05) Residue as the Unit of Software Architecture(46:31) Practical Way of Applying Residuality(49:03) The Goal of Architecture is Criticality(52:17) Bridging the Gap Between Architecture and Stakeholders(55:09) 3 Tech Lead Wisdom_____Barry O’Reilly’s BioBarry is a veteran Architect who has held Chief Architect positions at Microsoft among others. He has also been a startup CTO, the Worldwide Lead for the Solutions Architecture Community at Microsoft, and founder of the Swedish Azure User Group. He is also a PhD candidate in software design and complexity science.Barry is a regular speaker at international conferences and events, where he shares his insights and expertise. He is the Founder of Black Tulip Technology and the creator of Residuality Theory, which seeks to redefine architecture as the management of complexity.Follow Barry:LinkedIn – linkedin.com/in/barry-o-reilly-b924657/📚 The Architect’s Paradox – leanpub.com/architectsparadox📚 Residues: Time, Change, and Uncertainty in Software Architecture – leanpub.com/residuality📚 Book bundle – leanpub.com/b/residues_____Our SponsorsManning Publications is a premier publisher of technical books on computer and software development topics for both experienced developers and new learners alike. Manning prides itself on being independently owned and operated, and for paving the way for innovative initiatives, such as early access book content and protection-free PDF formats that are now industry standard.Get a 40% discount for Tech Lead Journal listeners by using the code techlead24 for all products in all formats.Like this episode?Show notes & transcript: techleadjournal.dev/episodes/212.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.