Podcasts about Technical debt

Recorded live at DX Annual, Abi Noda, co-founder and CEO of DX, joins Brian Houck of Microsoft to share an early look at DX's new research on AI's impact on engineering velocity.Drawing on data from a sample of DX customers, they discuss what companies are actually seeing as AI adoption matures. Most organizations in the study saw pull request throughput increase by 10 to 15 percent—far more modest than the 10x gains often promised in industry headlines.They explore why coding remains only a small part of developer work, where time saved by AI may be going, and the unintended consequences of moving faster, from shifting bottlenecks to “false velocity.” Abi also shares how engineering leaders are applying AI beyond coding and how DX is evolving its measurement framework to account for both human and agent productivity.Where to find Brian Houck: • LinkedIn: https://www.linkedin.com/in/brianhouck/ Where to find Abi Noda:• LinkedIn: https://www.linkedin.com/in/abinoda In this episode, we cover:(00:00) Intro(00:53) What motivated DX's research into AI's impact on engineering velocity(02:36) How DX designed the study and selected companies(04:54) What DX's data reveals about AI's impact on engineering throughput(06:31) Why PR throughput was the most practical metric to publish(08:21) Why AI productivity gains are lower than many leaders expected(10:24) How an all-in culture can amplify AI productivity gains(12:35) Why it's hard to track where AI-generated time savings are going(15:04) Unintended consequences of AI-driven productivity gains(17:12) Why leaders should look beyond coding to the rest of the SDLC(19:43) Cognitive debt and the human costs of AI-assisted development(21:33) How DX's AI measurement framework is evolving(24:42) How to make agents more effectiveReferenced:• DX Core 4 Productivity Framework • DORA, SPACE, and DevEx: Which framework should you use?• Time Warp: The Gap Between Developers' Ideal vs Actual Workweeks in an AI-Driven Era - Microsoft • Research• How Generative and Agentic AI Shift Concern from Technical Debt to Cognitive Debt• Measuring AI code assistants and agents

In this episode of Elixir Wizards, hosts Charles Suggs and Emma Whamond sit down with Saša Jurić, Elixir mentor and author of Elixir in Action, to discuss software craftsmanship in the age of AI. As AI coding tools become increasingly capable, Saša argues that the real challenge isn't generating code, it's maintaining quality, clarity, and shared understanding within a codebase. We explore the difference between correct code and good code, and why code is more than a set of instructions for a machine to execute. Code is also documentation, communication, and a long-term investment that future developers must be able to understand and maintain. Saša shares his concerns about the growing "theater of pull requests," where teams go through the motions of code review without creating meaningful opportunities for learning, feedback, or knowledge sharing. The hosts and Saša talk about practical ways to work effectively with AI, including taking smaller steps, carefully reviewing AI-generated code, and using AI as a collaborative tool rather than an autonomous developer. Throughout the discussion, Saša challenges the industry's obsession with speed and makes the case that the principles of good software development (incremental progress, clear communication, and human judgment) remain important in the age of AI. Key Topics Discussed The difference between correct code and good code Code as communication, documentation, and shared understanding The "theater of pull requests" and ineffective review practices How AI is changing software development workflows Using AI as a collaborator rather than a replacement Why smaller, incremental changes lead to better outcomes Human oversight in AI-assisted development Balancing development speed with maintainability Pull request size and review effectiveness Commit history as a tool for storytelling and context The risks of accumulating technical debt faster with AI Testing and validating AI-generated code Refactoring AI-generated solutions for clarity Applying agile principles to AI-assisted workflows The role of experience and judgment in software design Why software craftsmanship still matters in the age of AI Links mentioned Code Complete by Steve McConnell https://khmerbamboo.wordpress.com/wp-content/uploads/2014/09/code-complete-2nd-edition-v413hav.pdf Harness AI for DevOps, Testing, and AppSec https://www.harness.io/ Claude Code https://claude.com/product/claude-code Claude Code GitHub https://github.com/anthropics/claude-code Pull Request for Oban https://github.com/oban-bg/oban/pull/331 SMPP https://en.wikipedia.org/wiki/Short_Message_Peer-to-Peer OpenAI Codex https://chatgpt.com/codex/ Opus AI https://opus.ai/ Tidewave https://tidewave.ai/ Credo Static Code Analysis https://github.com/rrrene/credo https://smartlogic.io/podcast/elixir-wizards/s11-e09-static-code-analyzer-elixir-credo-ruby-rubocop/ Link to Sasa's X post https://x.com/sasajuric/status/2029522378196238503 Saša Jurić “Tell Me A Story” at Goatmire https://www.youtube.com/watch?v=GOrKfCs-mr0 https://meks.quest/blogs/the-theatre-of-pull-requests-and-code-review Looks Good to Me: Constructive Code Reviews by Adrienne Braganza https://www.manning.com/books/looks-good-to-me Towards Maintainable Elixir: Testing https://medium.com/very-big-things/towards-maintainable-elixir-testing-b32ac0604b99 TDD, Where Did It All Go Wrong (Ian Cooper) https://youtu.be/EZ05e7EMOLMSpecial Guest: Saša Jurić.

In their song, Everything to Everyone, the band Everclear gave voice to every IT team on the planet who struggles to keep the lights on due to the ever-rising tide of technical debt and SaaS licensing. "The hand you hold is the hand that holds you down!" Of course, they were likely not explicitly referencing the IT landscape, but the mantra surely sticks. Today, at long last, there is a ray of hope for these battle-tested administrators, in the form of Deterministic Enterprise-native AI that promises more deterministic results. While GenAI grabs all the headlines for writing everything from press releases to poetry, a handful of enterprise engineers have been busy crafting a hybrid solution that fuses the generative power of LLMs, with the determinism of enterprise systems of record. Register for this DM Radio to learn how today's innovators are building solutions that are agile and bulletproof. Host Eric Kavanagh will be joined by industry legend Sam Yen, former Chief Innovation Officer for JPMorganChance, now the GM for Everest Systems. He'll show how hybrid AI systems are eclipsing legacy architectures, and solving technical debt once and for all.

The Transformation Ground Control podcast covers a number of topics important to digital and business transformation. This episode covers the following topics and interviews:   What Is Technical Debt? Navigating ERP Cloud Migration (Brad Feakes, President of Estes Group) Cloud Doesn't Mean You're Less Locked In   We also cover a number of other relevant topics related to digital and business transformation throughout the show.  

Get featured on the show by leaving us a Voice Mail: https://bit.ly/MIPVM A practical rethink of how teams use Power Platform and Dynamics 365 to reduce technical debt, improve governance, and build sustainable solutions. The discussion centres on shifting from tech-first thinking to business outcomes, balancing low-code and pro-code principles, and preparing for AI and Copilot. The key insight is that long-term success comes from disciplined governance, reuse, and choosing when to adopt versus adapt. 

Hello gang, welcome to podcast 272. This is Jared and today, we're going to talk about Technical Debt. We extract one of the best laughs we can ever have on TSB and that is played at the end, and the line is part of the whole beginning too. We talk about some things from around the landscape, especially from what I have posted, so we'll keep our eyes on things. More blog posts later. More podcasts later. See you soon.

Sally Lait joins Robby Russell on Maintainable to explore software maintainability through a different lens… not just code quality, but how teams work together over time. Sally is a fractional technology leader and advisor with more than two decades in the industry. You can follow her on LinkedIn or Mastodon. They start with a familiar question: what makes software well maintained? Structure and standards matter, but Sally shifts the focus to signals around the edges… documentation, onboarding speed, knowledge sharing, and especially how confident people feel making changes. That confidence becomes the thread throughout the conversation. Teams with high confidence move faster and adapt more easily. Teams with low confidence hesitate, avoid parts of the system, and struggle to make progress… regardless of what the code looks like. Robby and Sally also dig into why maintenance work often struggles to get traction. It rarely speaks for itself. Leaders need to connect it to outcomes the business already cares about… risk, hiring, delivery speed, and long-term sustainability. Sally references a LeadDev panel she moderated on why maintenance still feels “stuck in 2015”: Why Software Maintenance Is Stuck in 2015. They also discuss modernizing legacy systems and moving away from long-standing in-house software… work that is rarely just technical. It requires trust, clear communication, and navigating the emotional attachment teams have to what they've built. The episode closes with advice for engineers joining older codebases: stay curious, build relationships early, and use onboarding gaps as opportunities to improve things for the next person. Episode Highlights [00:01:02] What Makes Software Maintainable: Technical quality matters, but cultural signals often tell the deeper story. [00:05:45] Why Progress Still Feels Slow: Even with improvements, teams can feel stuck due to perception gaps. [00:07:30] Communicating Small Wins: Lack of visibility into incremental progress impacts morale and confidence. [00:12:40] Influencing Without Manipulating: Maintenance work needs to be framed in business terms. [00:16:00] Technical Debt as a Hiring Problem: Outdated systems affect recruiting and retention. [00:20:22] Modernizing a Siloed System: Unlocking legacy data required both technical and organizational change. [00:26:55] Building Trust for Change: Surprise proposals fail… alignment takes time. [00:32:39] Letting Go of “Our Baby”: Replacing systems involves emotional and cultural dynamics. [00:46:25] Joining an Older Codebase: Practical advice for onboarding and building confidence quickly. Resources Mentioned Sally Lait Sally Lait on LinkedIn Sally Lait on Mastodon Why Software Maintenance Is Stuck in 2015 (LeadDev Panel) Lara Hogan The Murderbot Diaries by Martha Wells Death of the Author by Nnedi Okorafor Sally's Reading & Reviews Site Thanks to Our Sponsors! Your test coverage says 90%, but that might be misleading. Undercover CI looks at your Ruby pull requests and shows you which parts of your changes weren't tested- not just overall coverage, but what changed and what got missed, down to the method level. Visit undercover-ci.com and use code MAINTAINABLE for 15% off your first billing cycle. Free for public repos. Private repos with unlimited users also available. Turn hours of debugging into just minutes! AppSignal is a performance monitoring and error-tracking tool designed for Ruby, Elixir, Python, Node.js, Javascript, and other frameworks. It offers six powerful features with one simple interface, providing developers with real-time insights into the performance and health of web applications. Keep your coding cool and error-free, one line at a time! Use the code maintainable to get a 10% discount for your first year. Check them out! Subscribe to Maintainable on:Apple PodcastsSpotifyOr search "Maintainable" wherever you stream your podcasts.Keep up to date with the Maintainable Podcast by joining the newsletter.

What happens when AI writes code faster than anyone can test it? In this episode of Eye on AI, Craig Smith sits down with Dan Faulkner, CEO of SmartBear, to explore one of the most underappreciated risks of the AI coding boom. As tools like Claude Code and Codex push software development to unprecedented speed, the systems built to validate that software are being left behind. Dan makes a distinction that every engineering leader needs to hear: clean code passing unit tests is not the same as an application that actually works. Dan introduces the concept of application integrity, continuous and measurable assurance that your software does everything it was intended to do and nothing it was not. He explains why the gap between what AI builds and what teams actually validate is already creating hidden risk in production, and why that risk compounds the faster you ship. We also get into the new failure modes that agentic AI is introducing. Slop squatting, instruction inversion, cascading errors. These are not theoretical. They are happening now, at scale, in codebases that no human has fully read. Dan also walks through SmartBear's autonomy ladder framework and their newest product BearQ, a team of AI agents that explores your application, builds a knowledge graph, authors tests, runs them, and updates everything as your app evolves. The key distinction: it is built to augment human teams, not replace them. Finally, Dan shares his honest take on the future of software engineering. The fallacy was always that coding was the hard part. The hard part is knowing what to build. That skill is not going anywhere. Subscribe for more conversations with the people shaping the future of AI and emerging technology.   Stay Updated: Craig Smith on X: https://x.com/craigss  Eye on A.I. on X: https://x.com/EyeOn_AI   (00:00) Introduction and Dan Faulkner's Background  (01:05) What SmartBear Does: Testing and API Lifecycle Management  (03:27) AI Is Outpacing Application Testing  (07:51) Slop Squatting, Instruction Inversion and New AI Failure Modes  (17:31) Black Boxes, Technical Debt and the Expertise Crisis  (22:00) How to Avoid Self-Validating AI Systems  (24:11) The Autonomy Ladder and BearQ  (31:30) Why Testing Must Be Continuous and Everywhere  (36:31) Infrastructure Risk and Automation Bias  (44:11) The Future of QA and New Specialist Roles  (50:44) How Teams Use SmartBear Tools Today  (58:57) The Future of Software Engineering and Human Roles

In this episode, Jeffrey discusses technical debt.Email Jeffrey with any questions or feedback (jtefertiller@servicemanagement.us)Each week, Jeffrey will be sharing his knowledge on Service Delivery (Mondays) and Service Management (Thursdays). Jeffrey is the founder of Service Management Leadership, an IT consulting firm specializing in Service Management, Asset Management, CIO Advisory, and Business Continuity services.  The firm's website is www.servicemanagement.us.  Jeffrey has been in the industry for 30 years and brings a practical perspective to the discussions. He is an accomplished author with seven acclaimed books in the subject area and a popular YouTube channel with approximately 1,600 videos on various topics.  Also, please follow the Service Management Leadership LinkedIn page.

A lot of organizations are betting that AI will make their teams faster. Some of them are right. Most are solving the wrong problem.AJ Bubb, founder of MxP Studio and host of Facing Disruption, joins Peter and Dave to talk about what actually happens when AI lands in a development team without fixing the system around it. If engineers can't get approvals, can't get access, and spend half their day in meetings, AI just means they produce more output the organization still can't handle. That's not a tooling problem. It's a structural one.They also get into velocity without direction, what ownership really looks like when a ticket gets blocked, and why synthetic user testing might be the most polite way to avoid talking to actual customers.This Week's TakeawaysOwn the problem from the customer all the way down. When something is blocked, it's still yours until it moves.When an outcome surprises you in either direction, ask whether your model was wrong. Most teams take the win and move on. The ones that improve don't.Before reaching for a technical solution, ask why five times. The problem someone walks in with is usually the invitation to a conversation, not the actual problem.If this episode got you thinking, we'd love to hear from you. Drop us a note at feedback@definitelymaybeagile.com or leave a review on your podcast app. And if you know someone navigating AI adoption right now, send this one their way.

Businesses killed QA with bad org design, but with AI, is there potential for a near-term QA boom?Join Product Manager Brian Orlando and Enterprise Business Agility Consultant Om Patel as we discuss the systematic elimination of QA roles over the past decade and discuss why that decision is now backfiring.That's right, with AI-generated code accelerating at breakneck speed and nobody to properly check or test it, Brian and Om argue that we might be heading toward a cliff of technical debt that will make skilled QA professionals more valuable than ever.We discuss this potential future in five acts:1. The Expensive Lie: Let's Dev Do the QA (until we lay them off as well)2. The Coming QA Boom3. When and Will Businesses Move Software Risk Upstream4. Why Dev Didn't and AI Won't Replace QA5. The Case for Human-In-The-LoopWhether you're a QA professional worried about your career, a product manager who inherited testing responsibilities, or a leader considering QA cuts - this episode provides data-backed arguments for why the QA field may be on the verge of its biggest resurgence yet.#QualityAssurance #AI #AgileLeadershipStack Overflow Developer Survey 2023, Practitest State of Testing Report 2024, World Quality Report 2025 by Capgemini and Micro Focus, GitLab DevSecOps Report 2024, Google Code Review Quality Study 2023, McKinsey Technology Report 2025 (State of AI in 2025), Theo (t3.gg) video on the future of developer roles, Software Quality and Beer podcast by Bob Cruz and Matt Kubal (Checkpoint Technologies), Cooper Bench (AI coding benchmark study), W. Edwards Deming (quality management principles), Toyota Production System (quality ownership model), Eliyahu Goldratt (Theory of Constraints / systems feedback loops), Brook's Law, Melissa Perri, Playwright (test automation framework), Claude Code (Anthropic)LINKSYouTube: https://www.youtube.com/@arguingagileSpotify: https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Apple: https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596INTRO MUSICToronto Is My BeatBy Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

  Is your cloud foundation ready for the explosion of AI workloads, or are you about to scale technical debt at the speed of innovation? In this episode, I'm joined by Apurva Kadakia, Global Head of Cloud and Partnerships at Hexaware, an AI-first transformation company helping enterprises modernize the core systems that will determine whether their AI strategies succeed or stall. With a front-row seat to large-scale cloud programs across industries, Apurva explains why so many organizations that "moved to the cloud" still find themselves unprepared for what comes next, and why modernization-led migration has become a business priority rather than a technology upgrade. We unpack the real warning signs that cloud environments are not fit for AI, from monolithic architectures and spiraling compute costs to hidden integration complexity and security gaps that only surface at scale. Apurva introduces the idea of "clarity before cloud," a structured approach to understanding sprawling application estates, identifying what truly matters to the business, and matching each workload to the right modernization path using the five R's. It's a conversation that moves beyond theory into the practical decisions leaders need to make now if they want to avoid being locked out of future innovation. The role of AI inside the transformation journey is another major theme. Rather than treating AI as a destination, Apurva shares how AI-led and human-perfected assessment models are already accelerating application discovery, classification, and migration planning, completing the majority of the heavy lifting while keeping human judgment firmly in control. We also explore why governance cannot be an afterthought, and how a dedicated Cloud Transformation Office can drive adoption, reskilling, stakeholder alignment, and data readiness without slowing delivery. Looking ahead to a world of agentic systems and rapidly multiplying cloud workloads, this episode offers a clear message. The organizations that win will not be the ones that adopted cloud first, but the ones that modernized with intent. So as AI moves from experimentation to enterprise scale, are your applications, your architecture, and your operating model truly ready to support it, or is now the moment to rethink your path before the next wave hits?      

Two words that make most engineers shudder: code refactoring. Now raise the stakes — refactoring decades of legacy systems inside a large enterprise. A tech debt-heavy project of this scale needs a leader who has driven complex digital transformations, like Gayatri Narayan (formerly PepsiCo, Microsoft, Amazon). Now, as President of Technology at Builders FirstSource, Gayatri Narayan is achieving a 3–4x increase in engineering velocity since joining less than a year ago.  Gayatri joins host Yousuf Khan to unpack the strategy behind those results, including how to deploy AI across the SDLC, how to rigorously evaluate ROI on AI investments, and how to lead change across complex enterprise tech stacks.Key Moments: 01:30 – Why Construction Technology Is Ready for Transformation 04:05 – AI Strategy: Elevating UX and Customer Experience 08:20 – Evaluating AI Investments: ROI, NPV, and Operating Costs 12:45 – Achieving 3–4x Engineering Velocity 16:05 – Humans in the Loop: Craft, Code Review, and AI Amplification 18:35 – Where the Industry Gets AI Adoption Wrong 20:30 – Leadership Advice: Start with the Customer About Gayatri: Gayatri Narayan is a general management executive with more than 15 years of experience leading product, engineering, data science, and operations across global enterprises, with full P&L responsibility and a track record of driving profitable growth through digital transformation.  She currently serves as President of Technology at Builders FirstSource, where she leads enterprise technology strategy, modernizes legacy systems, and embeds AI into the software development lifecycle to accelerate innovation across the residential construction value chain.  Previously, she served as Senior Vice President of Digital Products and Services at PepsiCo and held multiple general management roles at Microsoft, including leading Product and Engineering for Intelligent Communications across Teams and Skype as well as Enterprise PaaS and SaaS businesses; she also held leadership roles at Amazon spanning Marketplace Transportation and Logistics and several major retail categories. Guest Highlights: “We've seen a three to four times increase in engineering velocity — especially in refactoring legacy systems where historically there was very little knowledge of how the system actually worked.” “With generative AI, companies that have existed for 20 or 30 years don't have to get bogged down by legacy stacks. They can embrace emerging technologies without spending 18 to 24 months just refactoring.” “It really comes down to efficiency of time. The developer's surface area of impact expands dramatically — it's not just about writing code anymore, it's about delivering business value faster.” Visit ciopod.com for more episodes. Subscribe on YouTube or follow on your favorite podcast platform so you never miss a conversation with today's top technology leaders. Our Sponsor:  Want to accelerate software development by 500%? Meet Blitzy, the only autonomous code generation platform with infinite code context, purpose-built for large, complex enterprise-scale codebases.  While other AI coding tools provide snippets of code and struggle with context, Blitzy ingests millions of lines of code and orchestrates thousands of agents that reason for hours to map every line-level dependency.  With a complete contextual understanding of your codebase, Blitzy is ready to be deployed at the beginning of every sprint. Blitzy handles the heavy lifting, delivering over 80% of the work autonomously. The platform plans, builds, and validates premium-quality code at the speed of compute, turning months of engineering into a matter of days. It's the secret weapon for Fortune 500 companies globally.  To hear how engineering leaders are transforming the way they deliver software, visit blitzy.com. Schedule a meeting with their consultants to enable an AI-Native SDLC in your organization today. Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

In this week's episode, Rob and Justin dig into the weird paralysis happening at enterprise scale. Fortune 500 companies are spending six months in high-level negotiations to build AI workflows that could be done in a week. IT departments, trained for decades to fear custom code, are watching their companies get lapped by competitors who just decided to turn the thing on. Everyone's releasing agent frameworks, every AI company's got one, some have more than one, and instead of clarifying things, it's freezing people up.. There's a massive gap between what AI can do right now and what most organizations are getting out of it. Justin calls it the capability overhang, and it's growing. Not because the technology isn't ready, but because of how businesses are approaching it. Rob's got stories from the field that'll make you feel like the guy in the manhole from Die Hard, waving his hands: "I can just do it right here. No really. Right here." You'll learn what it really means to unlock AI (spoiler: it's not about waiting for the tech to get better), why hoping for built-in solutions is a fantasy, and why Claude is now updating its own instructions when it screws up. If you've been wondering whether you're behind on AI or just appropriately skeptical of the hype, this one's for you. Also in this episode: Juan Garcia on Raw Data with Rob Collie Morpheus / The Matrix Die Hard Manhole scene

Aging network infrastructure is consuming maintenance dollars that should be funding modern, secure architectures, especially as agencies try to integrate AI. It's a spiral that deepens cyber risk and delays progress. We'll look at options for getting out of that cul‑de‑sac with Cisco's Senior Director for Technology Policy, Eric Wenger.See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

This week, I've been thinking about something slightly uncomfortable. Last weekend, I was reviewing one of my older architecture diagrams from five years ago. A cloud-native migration plan I was deeply proud of at the time. It was clean. Structured. Scalable. And then I asked myself: If I were to rebuild this today in the era of generative AI… Would I build it the same way? The honest answer? No. Not because it was wrong. But because our assumptions have changed. Two years ago, AI was a feature. Today, AI is shaping architecture decisions. We're not just designing systems anymore. We're designing systems that design, generate, predict, and automate. And here's the tension I keep seeing in enterprise conversations: Everyone wants AI. But very few are asking: "What technical debt are we creating while chasing it?" That's why today's conversation matters. Today, I'm joined by Maxim Salav, based in Australia, someone who works deeply in enterprise architecture and technical debt remediation. And this episode is not about hype. It's about responsibility. Because AI doesn't remove architectural complexity. In many cases, it amplifies it. Let's get into it. Chapters 00:00 Introduction to Technical Debt and Architecture 01:34 The Impact of AI on Technical Debt 04:12 Generative AI and Architectural Challenges 08:40 Adopting AI in Organizations 12:26 Building AI Strategies and Governance 17:33 Data Quality and AI Integration 22:43 Guardrails for AI Adoption Episode # 181 Today's Guest: Maxim Silaev, Technology Advisor and Enterprise Architect He is a technology advisor and enterprise architect with more than two decades of experience working with high-growth companies, complex systems, and business-critical platforms. Website: Arch-Experts What Listeners Will Learn: What technical debt really means in the AI era How generative AI can unintentionally increase hidden system risk Why architecture remains critical despite AI coding tools The importance of governance and verification layers in AI systems How large enterprises are cautiously integrating AI Why strategy must precede AI deployment The evolving role of enterprise architects in AI-native environments Resources: Arch-Experts

Becoming AI-first isn't about deploying more tools, but about changing how work gets done.In this episode, Laura Stevens breaks down why AI transformation is fundamentally a leadership and operating model challenge, not a technology one. The conversation explores how organizations must redesign workflows, confront technical debt, rethink roles and responsibilities, and build trust in AI systems to unlock real value. Drawing on patterns across industries, Laura explains why smaller organizations often move faster, how AI exposes hidden inefficiencies, and what leaders must do to shift from managing tasks to overseeing outcomes. This is a grounded, practical look at what AI-first actually means in practice - and why most organizations underestimate the change required.Dive deeper: Download your AI-first playbook hereTakeawaysAI transformation requires a redesign of organizational workflows.Technical debt can become a strategic bottleneck for AI adoption.AI should be integrated into business processes, not treated as a separate technology.Trust in AI is hindered by psychological barriers and fear of loss of control.Roles in organizations must shift from task execution to oversight and strategy.Smaller organizations often adapt to AI faster due to less legacy complexity.AI adoption should focus on outcomes rather than isolated use cases.Leadership must understand that AI changes how value is created in organizations.AI can expose existing complexities and inefficiencies in processes.The success of AI transformation depends on the willingness to rethink how work is done.

Legacy systems work. So why do companies waste millions rewriting them? In this episode of Arguing Agile, Product Manager Nisha Patel joins Product Manager Brian Orlando and Enterprise Business Agility Consultant Om Patel for a debate on the dangerous obsession with rewriting legacy systems — from COBOL to green screens — that still power ATMs, government systems, and Fortune 500 billing engines. Watch or listen as we discuss the myth that "modern" equals "better" and reveal how most rewrites fail because they ignore customer value, edge cases, and real ROI as well as other topics, such as:How Chesterton's Fence applies to code (Brian still doesn't know)How Developers kill software with Resume-Driven Development (RDD)How Finance kills software with spreadsheet-driven development (SDD)Why chasing "parity" kills innovationRisk Mitigation, or, framing technical debt in business termsIf you've ever worked on or tried to replace legacy systems, this episode will either give you nightmares, or help how you approach legacy systems while helping you also stop burning budget on vanity projects.#LegacyCode #ProductManagement #AgileCoachingREFERENCESAA148 - An Introduction to Software Development FinancesLINKSYouTube: https://www.youtube.com/@arguingagileSpotify: https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Apple: https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596INTRO MUSICToronto Is My BeatBy Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

This interview was recorded for GOTO Unscripted.https://gotopia.techRead the full transcription of this interview here:https://gotopia.tech/articles/408Michael Nygard - Chief Architect at Nubank & Author of "Release It!"Charles Humble - Freelance Techie, Podcaster, Editor, Author & ConsultantFULL TALK TITLEBuilding Software That Survives: Autonomy, Architecture & Alignment at ScaleRESOURCESMichaelhttps://www.linkedin.com/in/mtnygardhttps://twitter.com/mtnygardhttp://www.michaelnygard.comCharleshttps://bsky.app/profile/charleshumble.bsky.socialhttps://linkedin.com/in/charleshumblehttps://mastodon.social/@charleshumblehttps://conissaunce.comDESCRIPTIONMichael Nygard, author of the influential "Release It!" and Chief Architect at Nuank, discusses his journey from programmer to technical leader.In this conversation, he shares insights from major transformation projects at Sabre and Nubank, exploring the nuances of centralization versus autonomy, the often-misunderstood implications of Conway's Law, and how architectural boundaries can reduce the need for constant organizational alignment.He emphasizes that effective technical leadership involves more than reorganizations - it requires understanding communication structures, celebrating the right behaviors, and creating systems that enable teams to operate independently within well-defined boundaries.RECOMMENDED BOOKSMichael Nygard • Release It! 2nd Edition • https://amzn.to/3WJeKV8Michael Nygard • Release It! 1st Edition • https://amzn.to/3XCkiRfRichard Monson-Haefel • 97 Things Every Software Architect Should Know • https://amzn.to/3JdRYU2Charles Humble • Professional Skills for Software Engineers • https://www.conissaunce.com/professional-skills-shortcutPatterson, Grenny, McMillan & Switzler • Crucial Conversations • https://amzn.to/3LhGHTaYevgeniy Brikman • Fundamentals of DevOps and Software Delivery • https://amzn.to/3WMPMFUTod Golding • Building Multi-Tenant SaaS Architectures • https://amzn.to/3YfM49oJacqui Read • Communication Patterns • https://amzn.to/3E37lvvMatthew Skelton & Manuel Pais • Team Topologies • http://amzn.to/3sVLyLQJames Stanier • Become an Effective Software Engineering Manager • https://amzn.to/3vHrx1EBlueskyTwitterInstagramLinkedInFacebookCHANNEL MEMBERSHIP BONUSJoin this channel to get early access to videos & other perks:https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/joinLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

Is 'Move Fast & Break Things' just permission to be reckless?Join Product Manager Brian Orlando and Enterprise Business Agility Consultant Om Patel as they examine Mark Zuckerberg's (in)famous mantra and reveal how it may have metastasized from breaking code to breaking laws, teams, and even contributing to real human harm.Watch or listen as we explore the critical dimensions of this philosophy, including:BREAKING SOFTWARE: How the original meaning of 'break things' (emphasizing first-mover advantage) evolved from rapid iteration of code to justifying regulatory evasion and monopolistic behavior.BREAKING TEAMS: Using Harvard research that shows 'always-on' cultures decrease productivity by 20% and spike turnover to discuss how intensity without recovery is just exploitation (and what to do instead).BREAKING PEOPLE: Discussing the human costs of unchecked speed, from Facebook's alleged role in the Myanmar genocide to Uber's systemic harassment culture to Theranos's fraud.LEARNING OVER SPEED: We discuss Eric Ries's seminal work: The Lean Startup and how it went out of it's way to emphasize learning velocity over shipping velocity. WRONG (we guess)!PUSHING BACK (WITHOUT GETTING FIRED): We brainstorm for frameworks to use for challenging speed-obsessed leadership, including trade-off and discuss real-world experiences.Whether you're running a business, a product manager, or a team member just trying to keep up, this episode arms you with arguments and frameworks to advocate for ethical innovation.What's your take on 'move fast' culture? Have you seen it more of a positive or negative?#ProductManagement #TechEthics #AgileLeadershipREFERENCESMove Fast and Break Things by Jonathan Taplin (2017), Careless People: A Cautionary Tale of Power Greed and Lost Idealism by Sarah Wynn Williams, The Lean Startup by Eric Ries (2011), The Fearless Organization by Amy Edmondson (2018), Susan Fowler's blog 'Reflecting on One Very Very Strange Year at Uber' (February 2017), UN Human Rights Council 2018 report on Facebook and Myanmar, Harvard Business School research on always-on cultures (2009), Agile Podcast E22 - Interview with a Scrum Trainer: Fred Mastropasqua (August 2021), Extreme Ownership by Jocko Willink, The Social Network (film, 2010)LINKSYouTube https://www.youtube.com/@arguingagileSpotify: https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Apple: https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596Website: https://arguingagile.com/

#329: Vibe coding - the practice of casually prompting AI to generate code solutions - has become increasingly popular, but its limitations become apparent when applications need to scale beyond personal use. While AI-assisted development can be powerful for proof of concepts and small internal tools, the transition from vibe-coded solutions to production-ready applications often requires experienced engineers to rebuild from scratch. The conversation explores three distinct levels of software development: personal tooling, internal applications, and public-facing systems. Each level demands different approaches, with vibe coding being most suitable for the first category but potentially problematic as complexity increases. The analogy of cooking illustrates this well - anyone can make a simple meal, but feeding hundreds of people requires professional expertise and proper infrastructure. Technical debt in the AI era presents new challenges and opportunities. Traditional software engineering principles like DRY (Don't Repeat Yourself) and clean code practices may matter less when AI can quickly refactor and improve code. The future likely involves hybrid teams where business experts work alongside experienced engineers, with AI agents handling implementation details. Darin and Viktor examine how pair programming is evolving from developer-to-developer collaboration to human-to-AI partnerships, fundamentally changing how software gets built and maintained.   YouTube channel: https://youtube.com/devopsparadox   Review the podcast on Apple Podcasts: https://www.devopsparadox.com/review-podcast/   Slack: https://www.devopsparadox.com/slack/   Connect with us at: https://www.devopsparadox.com/contact/

The "vibe coding will kill SaaS" narrative is everywhere right now, and I think it's completely wrong. Yes, anyone can spin up a Lovable or Bolt.new project in an afternoon. But there's a fundamental confusion happening: people are mistaking software products for software businesses. SaaS was never really about the software — it was always about the service, the operations, the years of edge cases and integrations and customer conversations that make a product actually work. In this episode, I break down why vibe-coded solutions fall apart the moment real customers show up, why "comprehension debt" is the hidden killer of AI-built projects, and how we might need to shift our messaging to make the invisible 20% of our work visible to buyers who now think they could build everything themselves.This episode of The Bootstraped Founder is sponsored by Paddle.comYou'll find the Black Friday Guide here: https://www.paddle.com/learn/grow-beyond-black-fridayThe blog post: https://thebootstrappedfounder.com/vibe-coding-wont-kill-saas/The podcast episode: https://tbf.fm/episodes/427-vibe-coding-wont-kill-saas Check out Podscan, the Podcast database that transcribes every podcast episode out there minutes after it gets released: https://podscan.fmSend me a voicemail on Podline: https://podline.fm/arvidYou'll find my weekly article on my blog: https://thebootstrappedfounder.comPodcast: https://thebootstrappedfounder.com/podcastNewsletter: https://thebootstrappedfounder.com/newsletterMy book Zero to Sold: https://zerotosold.com/My book The Embedded Entrepreneur: https://embeddedentrepreneur.com/My course Find Your Following: https://findyourfollowing.comHere are a few tools I use. Using my affiliate links will support my work at no additional cost to you.- Notion (which I use to organize, write, coordinate, and archive my podcast + newsletter): https://affiliate.notion.so/465mv1536drx- Riverside.fm (that's what I recorded this episode with): https://riverside.fm/?via=arvid- TweetHunter (for speedy scheduling and writing Tweets): http://tweethunter.io/?via=arvid- HypeFury (for massive Twitter analytics and scheduling): https://hypefury.com/?via=arvid60- AudioPen (for taking voice notes and getting amazing summaries): https://audiopen.ai/?aff=PXErZ- Descript (for word-based video editing, subtitles, and clips): https://www.descript.com/?lmref=3cf39Q- ConvertKit (for email lists, newsletters, even finding sponsors): https://convertkit.com?lmref=bN9CZw

Is your solution architect a gatekeeper or an enabler? Join Product Manager Brian Orlando and Enterprise Business Agility Consultant Om Patel as they draw from their experiences to debate the reasons these roles - which should be natural partners - often find themselves at odds. It's a no-holds-barred look into the eternal conflict between product managers and solution architects!Watch or listen as we explore:1. Why the role exists and if it's even necessary2. Who owns technical decisions3. How PMs may be part of the problem4. Three conversations that never happen5. Identifying architects: shepherds vs. hoarders6. When and how to escalate (without destroying your career)They provide actionable takeaways including the "documentation test," the "decision autonomy test," and the "vacation test" to evaluate whether your architect is enabling or blocking your teams.Whether you're a product manager frustrated by architectural gatekeeping, a solution architect trying to add value without becoming a bottleneck, or a leader trying to resolve these conflicts, this episode offers you solid, practical takeaways that you can start trying today!#ProductManagement #SolutionArchitect #LeadershipTeam Topologies by Manuel Pais and Matthew Skelton, Empowered by Marty Cagan (2020), Five Dysfunctions of a Team by Patrick Lencioni (2002), Radical Candor by Kim Scott, Release It! by Michael Nygard (2017), The Goal by Eliyahu Goldratt, Arguing Agile Episode 67: Team Topologies, Arguing Agile Episode 235: Changing Your Message - Adaptive vs Manipulative Communication, Arguing Agile Episode 236: Why Product Managers Should Own PricingLINKSYouTube https://www.youtube.com/@arguingagileSpotify: https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Apple: https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596Website: https://arguingagile.com/

Jack Ellis recently shared that storing page views and custom events in separate database tables was his biggest mistake at Fathom Analytics. That got me thinking about my own data modeling decisions at Podscan—choices I made on day one that now, two years and 45 million episodes later, either enable or constrain everything I build. Today, I'm exploring how your data model doesn't just store information, it fundamentally shapes how you think about your product. From the simple decision of whether to include teams in your authentication system to the complex realities of running full-text search across terabytes of transcript data, I'll share the migrations, the blue-green deployments, and the hard lessons about building flexibility into both your infrastructure and your founder mindset.I'm running a time-limited Black Friday sale of The Bootstrapper's Bundle: all my books, all my courses, all formats, for $25 instead of $100+. Grab it here: https://tbf.link/bffThis episode of The Bootstraped Founder is sponsored by Paddle.comYou'll find the Black Friday Guide here: https://www.paddle.com/learn/grow-beyond-black-fridayThe blog post: https://thebootstrappedfounder.com/how-your-data-model-shapes-your-product/ The podcast episode: https://tbf.fm/episodes/426-how-your-data-model-shapes-your-product Check out Podscan, the Podcast database that transcribes every podcast episode out there minutes after it gets released: https://podscan.fmSend me a voicemail on Podline: https://podline.fm/arvidYou'll find my weekly article on my blog: https://thebootstrappedfounder.comPodcast: https://thebootstrappedfounder.com/podcastNewsletter: https://thebootstrappedfounder.com/newsletterMy book Zero to Sold: https://zerotosold.com/My book The Embedded Entrepreneur: https://embeddedentrepreneur.com/My course Find Your Following: https://findyourfollowing.comHere are a few tools I use. Using my affiliate links will support my work at no additional cost to you.- Notion (which I use to organize, write, coordinate, and archive my podcast + newsletter): https://affiliate.notion.so/465mv1536drx- Riverside.fm (that's what I recorded this episode with): https://riverside.fm/?via=arvid- TweetHunter (for speedy scheduling and writing Tweets): http://tweethunter.io/?via=arvid- HypeFury (for massive Twitter analytics and scheduling): https://hypefury.com/?via=arvid60- AudioPen (for taking voice notes and getting amazing summaries): https://audiopen.ai/?aff=PXErZ- Descript (for word-based video editing, subtitles, and clips): https://www.descript.com/?lmref=3cf39Q- ConvertKit (for email lists, newsletters, even finding sponsors): https://convertkit.com?lmref=bN9CZw

Welcome to another episode of Road to CTO, our series where we sit down with some of the most experienced and influential technology leaders in the world.In this episode, we talk with Dorion Carroll, a veteran with 35 years of tech leadership experience, former CTO at Zynga, VP at Amazon, and one of the most insightful engineering minds in the industry.From scaling engineering teams from 280 to 3,600 people, to navigating billion-dollar decisions, to understanding what truly makes a great CTO, Dorion shares the lessons, stories and frameworks that shaped his extraordinary career.If you're an aspiring CTO, an engineering manager, or simply passionate about how world-class tech organisations operate behind the scenes, this is a masterclass.Support the show

244 | "Qualität ist das beste Rezept" - auch für AI Startups, die den nächsten Hype jagen? Mental Load von Eltern als Audio-Pitch bei "Roast my Geschäftsidee" und frische Geschäftsideen von Sam & AlexPerfekte HiFi Systeme auf www.sonoro.com - mit Code "digitaleoptimisten" gibt es 1 Jahr mehr Garantie auf German Audio Design Systeme wie den neuen AVATON.Finde eine Geschäftsidee, die perfekt zu dir passt: ⁠digitaleoptimisten.de/quiz⁠Kapitel:(00:00) Intro(02:52) AI Blase in Sartp-Land: Qualität ist das beste Rezept?(23:10) Roast my Geschäftsidee: Audio Pitch Daddy Do(37:11) ca .36:00 Samuels Weisheiten für's Leben(46:56) Post von Optimisten → Retten LLMs am Ende den Journalismus?(55:00) Geschäftsidee von Alex: Event Buddy(1:00:32) Geschäftsidee von Samuel: Brocky HunterMehr Kontext:In dieser Unicorn Ideas Folge sprechen Alex und Samuel über die Wahrheit hinter dem aktuellen AI-Hype, warum viele AI-Startups gerade kollabieren, und was Gründer wirklich aus dem „TikTok-Startups“-Trend lernen müssen. Samuel teilt exklusive Insights zu Cluely, AI Coding Tools, dem Einbruch der Nutzerzahlen und warum Viralität kein Geschäftsmodell ersetzt.Alex bringt eigene Erfahrungen aus dem Bau von PodAgent ein – und erklärt, warum viele AI-Produkte in der Praxis nicht halten, was der Pitch verspricht.Außerdem in dieser Folge:Warum viele Startups heute nur für Viralität bauenWie gefährlich „Vibe Coding“ und massiver Technical Debt wirklich sindWelche Rolle VC-Hypes spielen und warum Gründer oft nur Reaktionen auf Investoren zeigenDie Frage: Sind wir mitten im ersten echten AI-Crash?Dazu gibt's zwei neue Geschäftsideen: Alex pitcht seinen „EventBuddy“ – einen ROI-Tracker für Networking Events. Samuel stellt „Brocki Hunter“ vor – die AI, die verborgene Schätze in Flohmärkten und Second-Hand-Läden findet und weiterverkauft.Und: Eine spannende Hörer-Einsendung zum Thema Mental Load, Kindern, Beziehung und unfairer Aufgabenverteilung. Eine Idee, die viele Eltern betrifft – und die Alex & Samuel gnadenlos auseinandernehmen.Diese Folge ist perfekt für alle, die sich für Business-Ideen, AI-Trends, Startups, Growth, Produktentwicklung und Entrepreneurship interessieren – und Lust auf ehrliche Hot Takes haben.Keywords:AI Hype, AI Startups, AI Crash, Startup Ideen, Business Ideen, Unicorn Ideas, Digitale Optimisten, Cluely, AI Coding Tools, Technical Debt, Vibe Coding, VC Hype, Entrepreneurship, Networking ROI, EventBuddy, Brocki Hunter, Mental Load, Eltern Startup, Business Podcast Deutsch, AI Trends, Gründer Podcast

After 20+ years as a software developer, AI coding assistants revealed a shocking truth: I never actually loved coding—I loved what code could accomplish. In this episode, I explore how transitioning from hand-crafting every line at Podscan to orchestrating AI-generated code exposed the fundamental difference between developers who cherish solving technical puzzles and entrepreneurs who prioritize shipping features that drive business value. This shift from programmer to orchestrator isn't just about tools; it's about letting go of a carefully constructed identity and embracing that for software entrepreneurs, pristine code was never the goal—rapid deployment, customer value, and business growth always were. If you're struggling with AI coding tools or clinging to perfectionist coding standards, this perspective might fundamentally change how you view your role as a technical founder.This episode of The Bootstraped Founder is sponsored by Paddle.comYou'll find the Black Friday Guide here: https://www.paddle.com/learn/grow-beyond-black-fridayThe blog post: https://thebootstrappedfounder.com/i-never-really-loved-coding-and-only-ai-made-me-realize-it/ The podcast episode: https://tbf.fm/episodes/424-i-never-really-loved-coding-and-only-ai-made-me-realize-it Check out Podscan, the Podcast database that transcribes every podcast episode out there minutes after it gets released: https://podscan.fmSend me a voicemail on Podline: https://podline.fm/arvidYou'll find my weekly article on my blog: https://thebootstrappedfounder.comPodcast: https://thebootstrappedfounder.com/podcastNewsletter: https://thebootstrappedfounder.com/newsletterMy book Zero to Sold: https://zerotosold.com/My book The Embedded Entrepreneur: https://embeddedentrepreneur.com/My course Find Your Following: https://findyourfollowing.comHere are a few tools I use. Using my affiliate links will support my work at no additional cost to you.- Notion (which I use to organize, write, coordinate, and archive my podcast + newsletter): https://affiliate.notion.so/465mv1536drx- Riverside.fm (that's what I recorded this episode with): https://riverside.fm/?via=arvid- TweetHunter (for speedy scheduling and writing Tweets): http://tweethunter.io/?via=arvid- HypeFury (for massive Twitter analytics and scheduling): https://hypefury.com/?via=arvid60- AudioPen (for taking voice notes and getting amazing summaries): https://audiopen.ai/?aff=PXErZ- Descript (for word-based video editing, subtitles, and clips): https://www.descript.com/?lmref=3cf39Q- ConvertKit (for email lists, newsletters, even finding sponsors): https://convertkit.com?lmref=bN9CZw

In this episode of SaaS Fuel, Thanos Diacakis shares battle-tested advice for scaling SaaS teams, streamlining delivery, and maximizing developer happiness. Drawing on his experiences at startups and tech giants like Uber, Thanos reveals counterintuitive strategies for improving software output, optimizing technical debt, rethinking backlogs, and harnessing new mental models. He breaks down the importance of incremental value, cross-functional collaboration, and avoiding the traps of over-planning. Whether you lead a small startup or an enterprise-scale engineering team, this conversation will challenge the way you think about speed, quality, backlog management, and long-term success.Key Takeaways00:00 "Checklists vs Software Complexity"03:19 Bug Fixing: Intuition vs Strategy08:24 Buckets: Features, Bugs, Investments, Risks09:47 Optimizing Feature vs. Platform Focus14:39 "Minimize Work in Progress"19:20 "Bug Backlogs: Input vs Output"20:39 Kanban Team Structure Guidelines26:38 "Rapid Progress in Coding Tools"28:21 "Minimal Planning, Bias for Action"31:48 "Delivering Incremental Customer Value"36:23 Collaborative Workflow Over Silos39:35 "Building Products That Inspire Use"42:53 "Accelerate: Building Effective Teams"44:11 Team Workflow Optimization Framework47:50 "Explore Mental Models Online"Tweetable QuotesWhy Slowing Down Software Releases Might Backfire: One of the things that would happen is if you slow down, how you ship to production is you'll have bigger batches and bigger batches, which means you might ship more bugs all at once and have to find them in a bigger QA cycle. — Thanos Diacakis "I also think we sometimes convince ourselves that we know more than we actually do and that we can plan a really long way out." — Thanos Diacakis Viral Product Development Mindset: "If you engage engineers and product in these creative discussions, you might find out, oh, I scoped out these 10 things, but turns out the customer gets 80% of the value from this one thing." — Thanos Diacakis Bureaucratic Bottlenecks in Big Companies: "They try to optimize locally for one particular function rather than optimize globally for shipping things out the door." — Thanos Diacakis Viral Topic: "Why Every Team Should Read Accelerate": So I think if I give anyone advices, if you haven't read Accelerate, then go read that book. Because it's basically lays out in terms of, and this is in terms of like core technical and procedural sort of infrastructural things that teams ought to have to be productive. — Thanos Diacakis SaaS Leadership LessonsBias Towards Action Over PerfectionAvoid waiting for perfect plans, especially with innovative projects; instead, learn by doing and iterating.Increase System VisibilityMake work in progress and team capabilities visible; this surfaces bottlenecks and areas for investment.Balance Short-Term and Long-Term GoalsStrategic investment in tooling, tech debt, and risk mitigation ensures sustainable delivery and value realization.Prioritize Collaboration Across FunctionsBreaking down silos between product, engineering, and design dramatically accelerates delivery and reduces defects.Ship Small, Ship OftenFrequent, incremental releases drive faster customer learning, boost agility, and reduce risk.Cultivate a Shared Language for OutcomesUse terms like investments and risk (not just features and bugs) to align business and technical priorities and drive meaningful...

(06:06) Brought to you by JellyfishAI tools alone won't transform your engineering org. Jellyfish provides insights into AI tool adoption, cost, and delivery impact – so you can make better investment decisions and build teams that use AI effectively. See for yourself at jellyfish.co/platform/ai-impact.Why do organizations constantly complain about having too much technical debt? Because they're solving the wrong problem.In this episode, Dr. Andrew Brown, author of “Taming Your Dragon: Addressing Your Technical Debt,” reveals a profound insight: technical debt isn't fundamentally a technical problem. It's a trade-off problem rooted in human bias, organizational systems, and economic incentives. Through his innovative “Technical Debt Onion Model,” Andrew shows how decisions about code quality happen across five interconnected layers, from individual cognitive biases to wicked problem dynamics.Andrew explains why the financial debt analogy is dangerously misleading and, more importantly, how others can rack up debt you'll eventually pay for. Drawing from behavioral economics, systems thinking, and organizational theory, he reveals why our emotions, not logic, drive most technical decisions, and how to work with this reality rather than against it.Key topics discussed:Why technical debt is a trade-off problem, not technicalHow emotions override logic in critical decisionsThe Technical Debt Onion Model framework explainedPrincipal-agent problems sabotaging your codebaseExternalities: who pays for shortcuts taken today?Why burning down debt is already too lateUlysses contracts for managing future obligationsSystems thinking applied to software developmentWicked problems: why different teams see different solutionsAI's impact on technical debt creationTimestamps:(00:00:00) Trailer & Intro(00:02:24) Career Turning Points(00:06:06) The Importance of Skilling Up in Tech(00:06:49) The Definition of Technical Debt(00:09:08) The Broken Analogy of Technical Debt as a Financial Debt(00:09:58) The Role of Human Bias and Organization Issues in Technical Debt(00:12:41) Tech Debt is a Trade-off Problem(00:13:07) Building a Healthier Relationship with Technical Debt(00:15:15) The Technical Debt Onion Model(00:18:17) The Onion Model: Trade-Off Layer(00:25:10) The Ulysses Contract for Managing Technical Debt(00:33:03) The Onion Model: Systems Layer(00:36:32) The Onion Model: Economics/Game-Theory Layer(00:41:50) The Onion Model: Wicked Problem Layer(00:48:10) How Organizations Can Start Managing Technical Debt Better(00:52:03) The Al Impact on Technical Debt(00:56:16) 3 Tech Lead Wisdom_____Andrew Brown's BioAndrew Richard Brown has worked in software since 1999, starting as an SAP programmer fixing Y2K bugs. He realized the biggest problems in software development were human, not technical, and has since helped teams improve performance by addressing these issues.Andrew coaches organizations on software development and quality engineering, focusing on technical debt, risk in complex systems, and project underestimation. He investigates how cognitive biases drive software problems and applies behavioral science techniques to solve them. His research has produced counterintuitive insights and fresh approaches. He regularly speaks at international conferences and runs a growing YouTube channel on these topics.Follow Andrew:LinkedIn – linkedin.com/in/andrew-brown-4b38062YouTube – @behaviouralsoftwareclub705Email – brownsensei@hotmail.com Taming Your Dragon – https://www.amazon.com/Taming-Your-Dragon-Addressing-Technical/dp/B0CV4TTP32/Like this episode?Show notes & transcript: techleadjournal.dev/episodes/239.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

What will be the SaaS Pricing Strategy 2026? In this episode, Joran sits down with Tjitte Joosten—known as T.J.—to discuss the evolving world of SaaS pricing and how founders can adapt to change without losing momentum. T.J. works full-time in pricing and packaging for SaaS and AI companies. Before that, he spent years in early-stage ventures, helping them find product-market fit and close major deals. Those experiences taught him how to win large accounts without over-discounting and how to leave room for long-term growth.Through that process, T.J. discovered that pricing is not just about numbers but also about psychology and behavioral economics. The same solution can sell for $10,000 or $50,000 depending on the story told. After meeting his co-founder, who was already working in pricing, T.J. transitioned into it full-time—and it became his passion.Their conversation explores how SaaS pricing is evolving, how to experiment with models safely, when to raise prices, how to communicate changes effectively, and how freemium models may evolve in the AI era.Key Timecodes(0:00) - B2B SaaS & AI Pricing Expert(0:05) - TJ Joosten on Value Storytelling(1:13) - Future of SaaS Pricing 2026(1:28) - Why Hybrid Pricing Wins(3:10) - The Pricing Switch Risk(3:27) - Technical Debt of Pricing(5:15) - How to Test New Pricing(6:40) - Entitlement & Packaging(7:13) - When to Raise Prices(8:49) - Timing Strategy: Netflix Case(10:04) - Communicating Price Changes(11:10) - Freemium in the AI Era(12:33) - The Cost of Free Users(13:38) - From $0 to $10K MRR(14:42) - Scaling to $10M ARR(15:56) - The Founder's Role in Pricing(16:32) - Connect with TJ Joosten

  Every software team, no matter its size or sophistication, has wrestled with the same quiet threat, technical debt. But what if the issue isn't just messy code or outdated frameworks, but something more human? That's the question Ernesto Tagwerker, Founder and CEO of OmbuLabs.ai, has been asking as he works at the intersection of AI, developer experience, and legacy modernization. In this episode of Tech Talks Daily, Ernesto joins me from Philadelphia to unpack why technical debt is so misunderstood and why the term has drifted far from Ward Cunningham's original metaphor. He argues that many teams treat it as a one-off cleanup task when, in reality, it's a living health issue that must be managed continuously. As he explains, "Every time you have to work around messy code, you're paying interest. And if later never comes, that interest piles up until progress grinds to a halt." We explore how AI is changing the way engineers think about remediation and developer experience (DX). Ernesto shares how OmbuLabs.ai uses AI agents to automate parts of the Rails upgrade process, scanning codebases for deprecations and generating actionable plans for clients. But his caution is clear, these tools are only as smart as the people orchestrating them. When used carelessly, they can generate invisible layers of new debt just as fast as they resolve the old. Ernesto also reflects on research from Google that reveals how "technical debt" varies wildly between teams and projects. He explains why leadership alignment is vital, how recurring surveys can help identify developer pain points, and why organizations should measure "technical health" rather than chase the unrealistic goal of zero debt. We discuss the cultural shift required for long-term success and why allocating even 10 to 20 percent of each sprint to DX improvements can dramatically reduce burnout and turnover. Finally, Ernesto offers his take on the future. AI will continue to automate repetitive work and surface smarter insights, but human oversight remains non-negotiable. In his words, "AI agents are only as good as their human operator." This conversation goes beyond code reviews and sprint retrospectives. It's about redefining what progress means in software development, healthier systems, happier developers, and smarter collaboration between humans and machines. Listen now to hear how Ernesto Tagwerker and OmbuLabs.ai are rethinking technical debt, DX, and AI-driven engineering for the decade ahead.   Tech Talks Daily is Sponsored by NordLayer: Get the exclusive Black Friday offer: 28% off NordLayer yearly plans with the coupon code: techdaily-28. Valid until December 10th, 2025. Try it risk-free with a 14-day money-back guarantee.

On today's Dear Heretics segment, Kelli and Nolan analyze why traditional bonus programs fail at early-stage companies, advocating for flexible sprint incentives and spot bonuses over rigid annual structures that create organizational debt.Support our Sponsor:Metaview is the AI platform built for recruiting. Check it out: https://www.metaview.ai/heretics* Our suite of AI agents work across your hiring process to save time, boost decision quality, and elevate the candidate experience.* Learn why team builders at 3,000+ cutting-edge companies like Brex, Deel, and Quora can't live without Metaview.* It only takes minutes to get up and running.KEEP UP WITH NOLAN + KELLI ON LINKEDINNolan: https://www.linkedin.com/in/nolan-church/Kelli: https://www.linkedin.com/in/kellidragovich/—For coaching and advising inquire athttps://kellidragovich.com/—TIMESTAMPS:(00:00) Introduction: The Bonus Program Question(01:04) The Cyclical Wave & Sales Incentives(01:42) Why Early-Stage Companies Struggle(02:46) The Coin-Operating Problem(03:26) The 96% Problem: Legacy & Recruiting Pressure(04:34) You Can't Put the Toothpaste Back(05:30) Equity Over Bonuses(06:09) Inconsistent Application Across Teams(06:43) Walking It Back Is Brutal(08:06) Sponsor: Metaview(09:28) Technical Debt vs People Debt(11:10) Second Order Consequences(12:31) MBOs Are a Fable(12:53) The Solution: Sprint Incentives(14:04) Surprise and Delight: Spot Bonuses(15:08) Discretionary Budgets & Agility(15:54) Final Thoughts: Avoid People Debt(15:59) Outro This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit hrheretics.substack.com

This episode is brought to you by ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Oberle Risk Strategies⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠: Insurance Broker and Insurance Due Diligence Provider for Search Funds and Other Small-to-Medium-Sized Businesses⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠  *This episode is brought to you by ⁠⁠⁠B⁠⁠⁠⁠⁠⁠⁠⁠oulay, the industry standard for Quality of Earnings, tax, and audit services, serving search fund entrepreneurs for 20+ years⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠*Chris Smith is the Managing Partner of Spellbound Partners, a a company that helps acquirors with technical due diligence, fractional CTO services, and outsourced development services, among other things. Chris has over 25 years of experience building software platforms, and is an expert in cloud computing and software as a service (SaaS). He has been a part of numerous founding startup teams and has led multiple teams through high-growth transitions.Much of what we discuss today is intended to uncover how much “technical debt” any given target company may possess within its code base. Though substantially every software company has some amount of technical debt, those that are weighed down by an asymmetric burden of it tend to experience very real business problems that non-technical acquirors and CEOs may not fully appreciate. As a result, prospective acquirors would be well served to thoroughly diligence the amount of technical debt possessed by any given target company, and proceed very carefully (or perhaps not proceed at all) with those companies who seem to possess much more than their fair share of it.

Technische Schulden: Code veröffentlichen und weiterziehen oder doch erst aufräumen?Technische Schulden fühlen sich oft nach Ballast an, können aber dein stärkster Hebel für Speed sein. Der Knackpunkt ist, sie bewusst und sichtbar einzugehen und konsequent wieder abzubauen. In dieser Episode sprechen wir darüber, wie wir technische Schulden strategisch nutzen, ohne uns langfristig festzufahren.Ward Cunningham sagt: Technische Schulden sind nicht automatisch schlechter Code. Wir ordnen ein, was wirklich als “Debt” zählt und warum Provisorien oft länger leben als geplant. Dann erweitern wir die Perspektive von der Code‑ und Architektur‑Ebene auf People und Prozesse: Knowledge Silos, fehlendes Code Review und organisatorische Entscheidungen können genauso Schulden sein wie ein any in TypeScript. Wir diskutieren sinnvolle Indikatoren wie DORA Metriken, zyklomatische Komplexität und den CRAP Index, aber auch ihre Grenzen. Warum Trends über Releases hilfreicher sind als Einzelwerte oder wie Teamskalierung die Kennzahlen beeinflusst. Dazu die Business Seite: reale Kosten, Produktivitätsverluste, Frust im Team und Fluktuation. Als Anschauung dient der Sonos App Rewrite als teures Lehrstück für akkumulierte Schulden.Wenn du wissen willst, wie du in deinem Team Technical Debt als Werkzeug nutzt, Metriken und Kultur klug kombinierst und den Business Impact sauber argumentierst, dann ist diese Episode für dich.Bonus: Wir verraten, warum Legacy allein keine Schuld ist und wie Open Source, Plattformteams und Standardisierung dir echte Zinsen sparen können.Unsere aktuellen Werbepartner findest du auf https://engineeringkiosk.dev/partnersDas schnelle Feedback zur Episode:

On today's Dear Heretics segment, Kelli and Nolan analyze why traditional bonus programs fail at early-stage companies, advocating for flexible sprint incentives and spot bonuses over rigid annual structures that create organizational debt.Support our Sponsor:Metaview is the AI platform built for recruiting. Check it out: https://www.metaview.ai/heretics* Our suite of AI agents work across your hiring process to save time, boost decision quality, and elevate the candidate experience.* Learn why team builders at 3,000+ cutting-edge companies like Brex, Deel, and Quora can't live without Metaview.* It only takes minutes to get up and running.KEEP UP WITH NOLAN + KELLI ON LINKEDINNolan: https://www.linkedin.com/in/nolan-church/Kelli: https://www.linkedin.com/in/kellidragovich/—For coaching and advising inquire athttps://kellidragovich.com/—TIMESTAMPS:(00:00) Introduction: The Bonus Program Question(01:04) The Cyclical Wave & Sales Incentives(01:42) Why Early-Stage Companies Struggle(02:46) The Coin-Operating Problem(03:26) The 96% Problem: Legacy & Recruiting Pressure(04:34) You Can't Put the Toothpaste Back(05:30) Equity Over Bonuses(06:09) Inconsistent Application Across Teams(06:43) Walking It Back Is Brutal(08:06) Sponsor: Metaview(09:28) Technical Debt vs People Debt(11:10) Second Order Consequences(12:31) MBOs Are a Fable(12:53) The Solution: Sprint Incentives(14:04) Surprise and Delight: Spot Bonuses(15:08) Discretionary Budgets & Agility(15:54) Final Thoughts: Avoid People Debt(15:59) Outro This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit hrheretics.substack.com

BONUS: Consulting is Different—How Consulting Contracts Work Against Agile Development, With Jakob Wolman and Wilko Nienhaus  In this BONUS episode, we explore the critical differences between building software as a consultant versus inside a product company. Jakob Wolman contributed an insightful article to the Global Agile Summit book examining how third-party software development operates under entirely different constraints than in-house product development. Joined by Wilko Nienhaus, CTO of Vaimo, a consulting company in Estonia, we dive into ownership dynamics, misaligned incentives, contracting challenges, and the business pressures that shape consulting—along with practical stories from the field about what really works. The Cobbler's Shoes Problem "I come back to the office from this workshop, and suddenly, with these eyes on looking for improvements in process, I just suddenly am hit by this revelation of why things are so slow here? Why are we working so inefficiently?" Jakob describes the striking paradox many consultancies face: they excel at helping clients improve their processes while their own internal operations remain inefficient. This "shoemaker's children" phenomenon reflects a fundamental challenge in consulting—the difficulty of investing in your own improvements when all energy flows toward billable client work. Digital agencies often have outdated or poorly implemented websites despite building sophisticated solutions for others, illustrating how consultancies struggle to apply their own expertise internally. Misaligned Incentives Create Antagonistic Dynamics "It's almost as if the clients are actually paying us to be slow, because our incentive is to spend more time on achieving what the client wants, because we get paid by the hour." The incentive structures in consulting create inherent conflicts that don't exist in product companies. Consultants typically bill by the hour, creating a perverse incentive to spend more time rather than deliver efficiently. Meanwhile, clients pursue business outcomes and want results as quickly and cheaply as possible. This fundamental misalignment leads to: Clients adopting a procurement mindset, treating software development like ordering from a catalog A "wall" between stakeholders and development teams that's even stronger than in product companies Antagonistic relationships where scope changes feel like financial traps rather than necessary learning Contracting processes that reinforce waterfall thinking even when both parties claim to want agility Wilko emphasizes that contracting has a huge impact on these dynamics, and companies must deliberately change their engagement models to break free from these patterns. The Budgeting Trap and Specification Overload "Because of this budgeting process where you now need to motivate what this budget does, or you need to spend that budget, you essentially create this necessity to define everything." Consulting projects often suffer from the same problem that plagued waterfall development: annual budgeting cycles that force stakeholders to cram everything into a single specification. When there's only one chance per year to secure funding, everyone stuffs the requirements document with every conceivable feature, leading to: Massive specifications that attempt to predict all needs upfront Endless discovery meetings and documentation that add cost without improving outcomes Developers working from outdated assumptions with delayed feedback Clients who don't really know what they want but feel pressured to specify everything Jakob points out the frustration that "we've already fixed this problem" in product development through iterative approaches, yet it keeps reappearing in consulting because of the separation between entities. Ownership and Quality in Consulting Environments "Skilled engineers will be frustrated if they're not allowed to do a proper job. People that have spent a lot of time in an environment where they're never allowed to do a proper job, or maybe even punished for doing a proper job, they will have given up, and not care." The difference in ownership between product and consulting development profoundly affects how engineers think about quality, technical debt, and long-term design. In product companies, developers know they'll maintain their code, creating natural incentives for quality. In consulting, the transient nature of engagements can erode quality standards. Key challenges include: Engineers knowing they won't return to the codebase, reducing long-term thinking Clients who lack technical expertise dictating approaches they don't understand Pressure to complete fixed-scope contracts regardless of quality trade-offs The role of estimates in forcing teams to "just complete this thing" even when learning suggests changes Wilko notes that teams controlled by clients versus teams managed as stable units by the consultancy show markedly different levels of ownership and engagement. Engineers want to do great work, but without real-world feedback loops, they may either overengineer based on theoretical ideals or give up on quality entirely. Breaking the Cycle: Going Live in Two Weeks "We said to them, what if we try to actually go live in a single sprint, which in most companies is 2 weeks. And they were like, nah, we're not so sure. And we said, don't worry, you're going to get everything you want in your scope by the end. But just let's try these first 2 weeks." Wilko shares a transformative story about an e-commerce project where his team convinced a client to abandon their two-year roadmap and instead focus on going live with something—anything—in two weeks. The goal: enable one existing customer to place one order for one product they already knew. This constraint forced radical prioritization. The team didn't need images, extensive product catalogs, or elaborate descriptions. They delivered a minimal but functioning system, and the results were revelatory: The client's internal discussion shifted from "we need everything" to "what should we prioritize next?" Real customer interaction revealed unexpected problems, like internal incentive conflicts where salespeople wouldn't direct customers to the website because it threatened their commissions Senior leadership embraced the iterative approach more readily than middle management The faster feedback cycle enabled genuine agility even in a consulting context This story demonstrates that iterative approaches are more likely to lead to success in consulting, and that senior leadership is often more receptive to faster feedback cycles than people expect. The key is changing the dynamic from "deliver a complete spec" to "let's go live quickly and learn." AI as a Game-Changer for Consulting Dynamics "The groundbreaking thing that's happening right now is AI, and it really feeds into this direction. Because instead of speaking, you can actually be building, you can see things, you can do stuff that you can really test in a much more real way than you could just a few years ago." Both Jakob and Wilko see artificial intelligence as a potential solution to many consulting challenges. AI tools enable rapid prototyping and visualization, allowing teams to show rather than tell. This addresses the fundamental problem that clients don't know what they want until they see it, by dramatically reducing the cost of creating tangible demonstrations that generate meaningful feedback. If you want to know more about how AI is reshaping programming, check out our AI Assisted Coding series of episodes.  Quality and Testing Should Not Be Negotiable "I just simply think it shouldn't be a choice. We have to be very firm on this is how we work. We are the experts you are paying us." When clients ask to skip testing, reduce code reviews, or cut corners on infrastructure, Jakob argues consultancies must stand firm. Quality practices shouldn't be line items that clients can negotiate away. One consulting company that works strictly with Extreme Programming principles demonstrates this approach—they don't explain every detail to clients, but they clearly establish that "this is how we do all our projects. It's not a choice." Wilko adds that testing often saves time rather than adding cost, serving as a development tool that eliminates repetitive manual verification. The challenge comes during estimation, where padding for testing can make consultancies less competitive, creating pressure to compromise on quality. Jakob emphasizes that some responsibility lies with consultancies themselves, which sometimes over-promise and underbid to win business, then struggle to deliver quality within unrealistic constraints. This "race to the bottom" hurts the entire industry. The Path Forward: Deliberate Collaboration "It is fixable in a consultancy setting as well. I've seen it. I've been part of it. But you have to be very deliberate in your collaboration with the customer." Success in consulting requires deliberately designing the engagement model to support iterative development: Working backward from customer needs, not forward from specifications Establishing short feedback loops with both client stakeholders and end users Creating stable teams rather than assembling ad-hoc groups based on client requests Changing contracting models to align incentives (as explored in Sven Ditz's article in the Global Agile Summit book on delivering incrementally) Being firm about quality practices while remaining flexible about features Using AI and rapid prototyping to generate early, concrete feedback The consulting model doesn't have to default to waterfall, but it requires conscious effort to overcome the structural forces pushing in that direction. Recommended Reading In this episode, we refer to multiple resources for further reading. Here's a list of those resources:  Secrets of Consulting by Gerald Weinberg The Global Agile Summit book, including articles by the speakers at the conference Real World Agility by Daniel Gullo The #NoEstimates book by Vasco Duarte Extreme Programming principles About Jakob Wolman and Wilko Nienhaus Jakob Wolman is an experienced engineering leader who knows how to build great software, and how to mess it up. He has worked in both product companies and consulting environments, giving him unique insight into the contrasts between these models. You can connect with Jakob Wolman on LinkedIn. Wilko Nienhaus is CTO of Vaimo, a consulting company in Estonia, where he focuses on the challenges of delivering software in a consulting environment. He concentrates on delivery mechanisms and technical solutions for challenging projects. You can connect with Wilko Nienhaus on LinkedIn.

Get featured on the show by leaving us a Voice Mail: https://bit.ly/MIPVM 

I was working with a customer recently that is trying to improve their processes. This was a large company, over 100,000 employees, though most of them aren't in the technology area. However, across many divisions and groups, there are a lot of developers and operations personnel who have tended to work in silos, managing their own applications and systems in disparate ways. In other words, doing software development the way most companies do it. Read the rest of Requiring Technical Debt Payments

  In this episode of Command Control Power, Joe and Sam catch up after attending a confidential Apple Technical Summit. They discuss the event's highlights, including networking opportunities and technical presentations. Sam shares his experience improving a client's old IT setup, moving them to modern managed services and security practices. Joe dives into his quest for an ideal phone solution with group SMS capabilities, ultimately considering sticking with RingCentral due to recent features supported by AI. The episode also touches on the importance and challenges of maintaining high-quality internet service at a fair price and explores the potential environmental impact of AI note-taking.   00:00 Introduction and Hosts Reunion 00:15 NDA Event and Apple Summit 01:31 Networking and Connections 03:01 San Jose and Big Basin Adventures 06:18 Technical Summit Insights 09:12 Funny Poolside Moments 11:03 Caseless Phones and Engineering Marvels 16:31 Coffee Talk and AeroPress Trivia 25:22 Billing Challenges and Solutions 28:29 Client Negotiations and Agreement 28:55 Email Security and Phishing 29:52 Security Training and Awareness 31:30 New Client with Technical Debt 33:45 Managed Services Plan Pitch 37:41 AI in Client Communication 38:32 Phone Service Saga 51:34 Optimum Fiber and Internet Deals 56:49 Concluding Thoughts and Future Topics

In this episode, I'm diving into a concept that may be quietly hindering your practice: technical debt. In short, technical debt occurs when you take shortcuts to save time, but they end up costing you more in the long run.I'll walk you through how technical debt shows up in your firm and why tackling this issue head-on is crucial to prevent burnout and boost your firm's overall productivity. I'll also share practical steps you can take to begin addressing your firm's technical debt. Get full show notes, transcript, and more information here: https://www.agileattorney.com/84Mentioned in this episode:Greenline.legal is Officially in BetaTo set up a demo of this software with me, talk through the workflow challenges and opportunities you have in your practice, and see how Greenline could help, click here: https://the-agile-attorney.captivate.fm/greenlinelegalGreenlineLegal Demo

Egil Østhus on LinkedIn: https://www.linkedin.com/in/egilconr/ Video of Egil talking about Unleash https://www.youtube.com/watch?v=HVBXxFZGVfc Go here to get started with Unleash: https://www.getunleash.io Four Pillars Excerpt from FeatureOps whitepaper and FeatureOps introduction There are four pillars of FeatureOps: The post 306 How Feature Flags are a form of Technical Debt first appeared on Agile Noir.

As dental practitioners, you surely put your blood, sweat, tears and years into growing your practice. But do you invest enough capital into protecting your practice with robust IT and security systems? The latest episode of The Dental Economist Show uncovers the reality of dental security today and why 70% of dental practices are at risk of a security breach. Tune in to hear host Mike Huffaker and Tom Barberio, Chief Information Officer at Thinc Forward, chat about the evolving landscape of dental technology and IT security - from how practices can avoid common technology pitfalls and effectively plan for infrastructure updates to how they can leverage the shift to cloud-based solutions. This conversation highlights that dental technology is shifting from being a cost center to becoming a true business enabler.

What happens when a distinguished engineer who shaped the cloud-native landscape decides to retire at 42? Kelsey Hightower, a pivotal figure in the Kubernetes community and former Google engineer, shares brutally honest insights from his 25-year journey. This isn't a conversation about the next hype cycle; it's a masterclass in the timeless principles of infrastructure, maintenance, and technical strategy. From the fallacy of technology replacement to the hard business realities that should drive engineering decisions, Kelsey provides a minimalist's guide to navigating complexity. Learn why most companies should embrace managed services, why engineers who can't link commits to revenue are at risk, and what the future of AI really means for the systems we build and maintain. Technical insights for CTOs and engineering leaders: -

In this insightful episode of SaaS Fuel, host Jeff Mains is joined by Mary Moore Simmons, VP of Engineering at Kibo. Together, they dive into the realities of building and scaling high-performing engineering teams, especially in fast-growth SaaS environments. Mary unpacks the nuanced challenges of evolving organizational processes, cultivating feedback-rich and psychologically safe cultures, handling “brilliant jerks,” and integrating AI to reduce grunt work and boost developer creativity. Tune in for a practical playbook on scaling teams, optimizing ways of working, and navigating technical debt as a business strategy, not just a developer's gripe.Key Takeaways[00:00:00] Feedback-Fueled Leadership: Mary's greatest fear as a leader is not knowing where she or her team might be going wrong—emphasizing feedback as the antidote to blind spots and organizational toxicity.[00:04:53] Process Check: When engineering processes feel slow or clunky as you scale, it's a sign to revisit and adapt. The right process should always speed teams up, not slow them down.[00:06:52] Culture First Hiring: Early hiring mistakes often relate to compromising on culture or failing to address culture misfits as teams grow. Brilliant jerks cost teams more in the long run, even if they are individually productive.[00:14:50] Handling Exits with Transparency: Delivering clear expectations and feedback means no one is surprised by tough decisions; transparent communication helps maintain trust when high-performers are let go for culture reasons.[00:20:38] Normalizing Feedback: Build an environment where feedback is everyday and safe—not just a scary signal of things going wrong. Celebrate when people speak up early and often.[00:27:00] AI Adoption: AI tools are powerful but still come with learning curves. Early adoption requires empathy and encouragement, especially in startups, and the biggest impact comes from knowledge sharing among engineers.[00:44:44] Technical Debt as Strategy: Make the business case for addressing technical debt—frame it with impact, not just engineering complaints, to get real buy-in from business leadership.Tweetable Quotes"My greatest fear as a leader is that I'm messing everything up and no one's telling me because they're too afraid." — Mary Moore Simmons"Process should always be speeding people up, not slowing them down." — Mary Moore Simmons"Hiring a brilliant jerk might make you faster today, but it will drag your team tomorrow." — Mary Moore Simmons"Feedback should be constant and small—don't let it become a scary event." — Mary Moore Simmons"Technical debt is not a developer gripe. It's a strategic conversation with real business impact." — Jeff Mains"AI tools double my speed, but they can also take me ten times in the wrong direction if I'm not paying attention."— Mary Moore SimmonsViral Topic: Amplifying Teams with AI"It's less about automation and more about amplification so if you're building a team, evolving your culture, or just trying to make scaling a little less chaotic, this episode has the clarity you didn't know you needed." — Jeff MainsAI & Automated Testing: "without automated testing, everything breaks. And I've experienced that. I think probably a lot of other founders have experienced that." — Jeff MainsSaaS Leadership LessonsLead with Feedback Openness: Proactively create a culture where feedback is routine, safe, and celebrated—not something to fear.Prioritize Psychological Safety: The best innovation happens when team...

What happens when two experienced CTOs sit down to debunk the latest tech trends? Raz Schweiger-Shuty, CTO at auxmoney, joins Tobi for an unfiltered discussion about the hypes, myths, and wastes of resources that plague modern tech companies. After taking over a 17-year-old fintech platform with no prior CTO, Raz made controversial decisions that flew in the face of conventional wisdom: stopping a microservices migration, questioning Kubernetes adoption, and focusing on measurable business value over engineering trends. His ""dinosaur CTO"" perspective offers a refreshing antidote to tech hype. This conversation cuts through the noise with practical insights on: •

Melanie Sumner: Why Continuous Accessibility Is a Strategic AdvantageMelanie Sumner, Product Accessibility Lead for Design Systems at HashiCorp, joins Robby to talk about what it takes to scale accessibility across legacy products—and how aligning design and engineering processes creates lasting change. Melanie shares her work making Ember.js more accessible, her team's philosophy behind their design system, and why she treats accessibility like any other technical concern.From the pitfalls of nested interactive elements to the strengths of Ember's conventions and codemods, this conversation offers a roadmap for integrating accessibility into every layer of product development.Melanie also reflects on why she trademarked the term Continuous Accessibility, how it fits into product lifecycles, and what other frameworks can learn from the Ember community's approach.“Accessibility is a technical problem with a technical solution.”Melanie joins us from Chicago, Illinois.Episode Highlights[00:01:00] What Well-Maintained Software Looks Like: Consistency, purpose, and bridging design and engineering[00:02:30] Building a Unified Design System Across 10+ Legacy Products[00:03:30] Creating Component Requirements Before Design or Code[00:05:00] Designing with Accessibility Defaults—and Providing Bridges for Legacy[00:07:00] How Ember's Conventions Help Scale Front-End Systems[00:09:30] Who Uses Ember—and Why It's a Fit for Teams with Big Requirements[00:13:30] Technical Debt in Design Systems and the Cost of Rushing[00:16:30] How They Future-Proof Components and Avoid Over-Engineering[00:19:00] What “Continuous Accessibility” Means in Practice[00:21:00] Accessibility Testing and the Limits of Automation[00:23:00] Common Accessibility Mistakes: Nested Interactives and Misused DIVs[00:24:30] Keyboard Navigation as a Litmus Test[00:26:00] Text Adventure Games and Accessibility as a Playable Experience[00:28:30] The Origin of Her Accessibility Journey at UNC Chapel Hill[00:31:00] Why She Avoids Framing Accessibility in Emotional Terms[00:32:45] Compliance as a Business Driver for Accessibility[00:35:00] Open Source Work on Testing Rules Across Frameworks[00:38:00] The Navigation API and Fixing Single-Page App Accessibility[00:40:30] HTML's Forgiveness and the Illusion of “Good Enough”[00:43:00] Advice for Engineers Advocating for Accessibility Without Authority[00:46:45] Book Recommendation: Cradle Series by Will Wight[00:48:30] Where to Follow Melanie: melanie.codesLinks and ResourcesMelanie's WebsiteHelios Design System at HashiCorpCradle Series by Will WightEmber Community SurveyA11y Automation GitHub ProjectAxe-coreFollow Melanie:GitHubLinkedInThanks to Our Sponsor!Turn hours of debugging into just minutes! AppSignal is a performance monitoring and error-tracking tool designed for Ruby, Elixir, Python, Node.js, Javascript, and other frameworks.It offers six powerful features with one simple interface, providing developers with real-time insights into the performance and health of web applications.Keep your coding cool and error-free, one line at a time! Use the code maintainable to get a 10% discount for your first year. Check them out! Subscribe to Maintainable on:Apple PodcastsSpotifyOr search "Maintainable" wherever you stream your podcasts.Keep up to date with the Maintainable Podcast by joining the newsletter.

BONUS: Zach Goldberg shares how to build high-performing engineering teams and master the startup CTO role In this BONUS episode, we dive deep into the world of startup leadership with Zach Goldberg, author of The Startup CTO's Handbook. We explore the critical transition from engineering to leadership, the art of balancing technical debt with startup urgency, and the communication skills that separate great CTOs from the rest. The Genesis of The Startup CTO's Handbook "My original training in software engineering was not enough for being a leader. All the people and leadership skills, I had to learn on my own." Zach's journey to writing The Startup CTO's Handbook began with a stark realization about the gap between technical training and leadership reality. Despite his classical software engineering background, he discovered that the people and leadership skills required for CTO success had to be self-taught. The book emerged from a growing Google Doc of topics and frameworks addressing the leadership and management challenges that CTOs consistently face - from hiring and performance management to making strategic decisions under pressure. Today, we can either buy the digital/print book on Amazon, or read the book on GitHub.  In this segment, we also refer to the book The Great CEO Within. Learning to Truly Learn: The Max Mintz Story "Max only cared about my ability to learn - to get curious about something hard. He wanted to help me deal with complexity." Zach opens his book with a deeply personal story about his mentor, Max Mintz, who fundamentally changed his approach to learning during what he calls "the most impactful single coffee" of his life. Over 1.5 years of conversations, Max taught him that true learning isn't about accumulating facts, but about developing curiosity for hard problems and building the capacity to handle complexity. This lesson forms the foundation of effective CTO leadership - the ability to continuously learn and adapt in an ever-changing technical landscape. The Three Critical CTO Mistakes "As a CTO, the most important 3 things: people, people, people. Do the people have the right energy, the right passion? Assemble the right team." Zach identifies consistent patterns in startup CTO failures across his experience. The first and most critical mistake is undervaluing people decisions - failing to prioritize team energy, passion, and the right assembly of talent. The second category involves investment mistakes, particularly the challenge of balancing short-term survival needs with long-term technical goals. In startups, the ROI timespan is exceptionally short, requiring optimization for immediate objectives rather than hypothetical scale. The third mistake is treating technology as religion rather than tools, losing sight of what the business actually needs. Optimizing for Velocity and Developer Experience "You are optimizing for velocity! What are you doing to help developers get their work done? Look at developer experience as a metric." Successful startup CTOs understand that velocity - the time from idea to valuable market delivery - is paramount. This requires a fundamental shift in thinking about technology decisions, focusing on features that deliver real customer value rather than technical elegance. Zach emphasizes measuring developer experience as a key metric, recognizing that anything that helps developers work more effectively directly impacts the company's ability to survive and thrive in competitive markets. The Professional Skill Tree Concept "It's like a character progression in an RPG. When we learn one type of skills, we don't learn other types of skills. We make investments every day and we have a choice on where we learn." Drawing from gaming metaphors, Zach explains how technical professionals often reach Level 100 in engineering skills while remaining Level 1 in management. The skill tree concept highlights that every learning investment is a choice - time spent developing one skill area means less time available for others. For engineers transitioning to leadership, the key is recognizing opportunities to serve as tech leads, where they can begin setting culture and quality standards while still leveraging their technical expertise. Balancing Kaizen with Startup Urgency "Pick the high-impact debt, and pay that down. This is not always easy, especially because we also need to pick what debt we don't invest on." The tension between continuous improvement and startup speed requires sophisticated thinking about technical debt. Using financial analogies, Zach explains that technical debt has both principal and interest components. The key is identifying which debt carries the highest interest rates and can be paid down most quickly, while consciously choosing which debt to carry forward. This approach maintains the healthy tension between quality and speed that defines successful startup engineering. The Power of Audience Empathy "The single hardest skill, especially for very tech leaders is that of 'audience empathy.' When you explain ideas to people, you usually assume a lot - but they might not." According to Zach, the most undervalued communication habit for startup tech leaders is developing audience empathy. Technical leaders often suffer from the curse of knowledge, assuming their audience shares their context and understanding. The solution requires deliberately considering what the audience already knows before crafting any communication, whether it's explaining technical concepts to non-technical stakeholders or providing clear direction to team members. In this segment we refer to the concept of “the curse of knowledge”, a cognitive bias that occurs when a person who has specialized knowledge assumes that others share in that knowledge. About Zach Goldberg Zach Goldberg is a seasoned technical entrepreneur, executive coach, and author of The Startup CTO's Handbook. With a founder's mentality and a passion for systems thinking, Zach helps engineering leaders build high-performing teams. He also founded Advance The World, a nonprofit inspiring youth in STEM through immersive experiences. You can link with Zach Goldberg on LinkedIn, and visit Zach's website at CTOHB.com.

CTO Series: Jussi Mononen on the Human Side of Software Development and Technical Leadership In this CTO Series episode, we explore the intersection of technology and people with Jussi Mononen, CTO of CarbonLink. Drawing from his extensive experience as an Agile practitioner and technical leader, Jussi shares valuable insights on effective software development, technical strategy alignment, and the critical human elements that drive successful technology implementations. The Transformative Power of Agile "It's all about people." Jussi's journey as a technology leader was fundamentally shaped when he discovered Agile methodologies. Coming from a background of waterfall-like approaches to software development, the introduction of Agile principles opened up a broader perspective that transformed his view of the profession. What began as technical work creating billing software evolved into a deeper understanding of the collaboration challenges in problem-solving. This shift helped Jussi develop a more humanistic and holistic approach to software development, recognizing that the human dynamics are often more complex than the technical challenges themselves. Every line of code eventually becomes a liability, as software is maintained over decades Software is only truly "done" when you remove the plug and it no longer exists Direct communication with customers is essential for understanding the real problems that need solving Balancing Technical Strategy with Business Needs "Be careful what you choose in terms of technology as you need to maintain it forever—hopefully." Creating a technical strategy that aligns with business objectives while remaining adaptable requires careful consideration of both immediate and long-term factors. Jussi emphasizes the importance of considering maintainability over a decade-long horizon while organizing technology stacks that don't limit organizational agility. When selecting technologies, consider whether you can find people already familiar with your tech stack Evaluate whether your technology choices allow you to fulfill the responsibilities your customers pay you to handle Be prepared to abandon technologies that aren't working, despite the sunk cost Structure your technical organization to maximize speed and adaptability Fostering Collaboration Between Tech and Business "It's not about 'who wins,' it's about making good decisions." Effective collaboration between technical and business units is built on foundations of respect and trust. As a self-described optimist about humanity, Jussi approaches cross-functional work by giving respect to colleagues and trusting them to make sound decisions within their domains of expertise. Listen carefully to people and make a genuine effort to understand their perspectives Focus on making well-considered decisions rather than striving for theoretical "best" decisions Remember that people develop software, not processes or tools—maximize each team member's potential Create environments where differing viewpoints are valued as inputs to better decision-making Strategic Roadmapping and Adaptability "We constantly seek information about what might be changing." Maintaining a clear vision of the future while remaining adaptable is a critical balancing act for technology leaders. Jussi's approach involves maintaining a rolling two-quarter roadmap that provides directional clarity while incorporating new information and signals from various sources. Review and revise roadmaps weekly to incorporate new information Use tools like Trello to maintain lists of priorities and possibilities Actively seek diverse signals about changing requirements and technologies Use the roadmap to communicate investment priorities to stakeholders like the board Overcoming Complex Technical Challenges "Someone needs to give enough love to the items in the backlog." The most significant challenge in Jussi's career came during a 4.5-year project reimplementing critical university systems that had been in use for over 20 years. This complex undertaking highlighted the importance of people skills alongside technical capabilities when managing diverse stakeholders with conflicting needs. Be prepared to handle conflicting needs and requirements from different stakeholders Establish a shared direction before attempting to solve detailed technical challenges Recognize that many critical challenges in large projects are about people, not technology Give proper attention to backlog items to ensure they receive the consideration they deserve Leadership Philosophy and Learning "Choose the context more accurately. Involve yourself with people you look up to." Rather than pointing to a single book that influenced his approach to technical leadership, Jussi emphasizes the importance of context and learning from those around you. His leadership philosophy centers on carefully selecting environments with admirable people and absorbing knowledge through direct experience and observation. Understand the specific context you're operating in before applying generic principles Surround yourself with people whose approach and values you respect Learn continuously from the practical experiences of peers and colleagues About Jussi Mononen Jussi is a problem solver, programmer and business-to-technology translator. People side of software systems development, as he often says: "it's all about people".He has both tech and people street cred, being a long time Agile practitioner, and now the CTO of a promising scale-up in Helsinki: CarbonLink. You can link with Jussi Mononen on LinkedIn.

Aatish Nayak is the Head of Product at Harvey where he oversees product vision, strategy, design, analytics, marketing, and support. This is his third hypergrowth AI unicorn having previously held product leadership roles at Scale AI from 40 to 800 people, and Shield AI from 20 to 100 people.  In Today's Episode We Discuss: 04:21 Biggest Product Lessons from Scale AI 7:18 Why Product Managers Are Wrong: They are not the CEO of the Product 12:28 Why Market Selection is More Important than Anything Else 16:40 If Distribution is King then Product is President 22:06 Effective Product Strategy and Execution 26:24 How to Write the Best PRDs 31:01 Balancing New Features and Technical Debt 33:17 Analysing Retrospectives and Postmortems 33:55 Introduction to Pre-mortems 38:25 Biggest Product Mistakes and Lessons Learned 41:40 Evaluating AI Models and Lessons Learned 45:03 The Future of AI in Product Management 55:21 What Should Product People Learn to Win in a World of AI 59:37 The AI Talent War in San Francisco 01:01:26 Quickfire Round  

Gaurav Misra is the co-founder and CEO of Captions, an AI-powered video creation company and one of the most successful consumer AI products in the world today. Previously he was a product leader at Snap, where he created the design engineering function and spent years helping develop features used by hundreds of millions of users worldwide. With a background in both engineering and design, Gaurav brings a unique cross-functional perspective to product development.What you'll learn:1. Why the “ship a marketable feature every week” approach helps his team stay focused and the product stay top of mind for users amid constant AI breakthroughs2. How to balance rapid shipping with maintaining quality by cutting scope rather than compromising on timelines3. The “secret roadmap” strategy that helps Captions develop breakthrough features competitors never see coming4. Why taking on strategic technical debt is essential for startups to outpace larger companies5. How Captions accidentally ignored their most successful product for 1.5 years (and why it still grew to 500K users with no updates or support)6. How Snap's unique product development approach—with designers functioning as PMs—enabled their success as the last major social network to break through7. Why AI video will transform marketing before other industries—Brought to you by:• Brex — The banking solution for startups• Paragon—Ship every SaaS integration your customers want• Coda—The all-in-one collaborative workspace—Find the transcript at: https://www.lennysnewsletter.com/p/how-to-win-in-the-ai-era-gaurav-misra—Where to find Gaurav Misra:• X: https://x.com/gmharhar• LinkedIn: https://www.linkedin.com/in/gamisra1/—Where to find Lenny:• Newsletter: https://www.lennysnewsletter.com• X: https://twitter.com/lennysan• LinkedIn: https://www.linkedin.com/in/lennyrachitsky/—In this episode, we cover:(00:00) Gaurav's background(04:47) The exciting era of AI and startups(09:30) Staying top of mind(11:26) Tips for staying focused(13:14) Shipping marketable features weekly(19:03) Managing technical debt in startups(25:31) Snap's unique product development approach(32:09) Brainstorming with AI(35:09) What Snap got right(41:06) Scaling with a small, agile team(49:33) The shift toward prototyping in product management(51:47) The product manager role(55:40) Snap's mission and product decisions(01:02:13) The future of AI-generated video(01:10:20) Leveraging AI for marketing(01:14:37) Failure corner(01:20:21) Lightning round and closing thoughts—Referenced:• Snap: https://www.snap.com/• Captions: https://www.captions.ai/• Iron Man on Disney+: https://www.disneyplus.com/movies/iron-man/6aM2a8mZATiu• J.A.R.V.I.S.: https://en.wikipedia.org/wiki/J.A.R.V.I.S.• Cursor: https://www.cursor.com/• Devin: https://devin.ai/• Eye contact: https://www.captions.ai/eye-contact• Nvidia: https://www.nvidia.com• Descript: https://www.descript.com• Evan Spiegel on LinkedIn: https://www.linkedin.com/in/evan-spiegel-8ab74034a/• TikTok: https://www.tiktok.com/• Spotlight: https://www.snapchat.com/spotlight/• Building product at Stripe: craft, metrics, and customer obsession | Jeff Weinstein (Product lead): https://www.lennysnewsletter.com/p/building-product-at-stripe-jeff-weinstein• Patrick Collison on X: https://x.com/patrickc• DeepSeek: https://www.deepseek.com/• ByteDance Goku: New video generation AI model, better than OpenAI Sora: https://medium.com/data-science-in-your-pocket/bytedance-goku-new-video-generation-ai-model-better-than-openai-sora-56c017a320a5• Will Smith eating spaghetti and other weird AI benchmarks that took off in 2024: https://techcrunch.com/2024/12/31/will-smith-eating-spaghetti-and-other-weird-ai-benchmarks-that-took-off-in-2024/• Silo on AppleTV+: https://tv.apple.com/us/show/silo/umc.cmc.3yksgc857px0k0rqe5zd4jice• Severance on AppleTV+: https://tv.apple.com/us/show/severance/umc.cmc.1srk2goyh2q2zdxcx605w8vtx• Linear: https://linear.app/• Superhuman: https://superhuman.com/• Notion: https://www.notion.com• Perplexity: https://www.perplexity.ai/• OmniHuman-1 AI Video Generation Looks Too Real: https://www.youtube.com/watch?v=fY0KB516m-E—Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@lennyrachitsky.com.—Lenny may be an investor in the companies discussed. Get full access to Lenny's Newsletter at www.lennysnewsletter.com/subscribe