Podcasts about tech debt

Welcome to the podcast featuring Hope Gurion, an esteemed product leadership coach. She is recommended by Marty Cagan in his book, Transformed, has moderated product leadership councils with Phyl Terry's Collaborative Gain, and works with Teresa Torres in training teams on Continuous Discovery Habits. In this episode, Hope delves into her extensive background in product management, sharing insights from over 25 years in the tech industry, her roles as Chief Product Officer, and SVP of Product. She discusses her transition from consulting to coaching, offering valuable guidance on becoming outcome-oriented and enhancing team effectiveness. Hope covers the challenges of finding the right company fit, the nuances between training and coaching, and key strategies for cross-functional collaboration. Tune in for actionable advice on elevating your product management career.00:00 Introduction and Welcome00:39 Hope Gurion's Background01:54 Transition to Coaching03:37 Challenges in Product Leadership04:55 Coaching and Training Approach07:25 Importance of Discovery in Product Management09:47 Balancing Training and Coaching15:57 Selecting the Right Coach18:51 Defining Success in Product Leadership21:33 Peer-Based Coaching vs. One-on-One Coaching28:23 Transformation in Organizations39:57 Podcast Origin Story and Conclusion

In this episode, Amir sits down with Brent Keator, an expert advisor at Primary Venture Partners, to unpack one of the most debated engineering challenges: tech debt versus reengineering. They explore how to define tech debt, when to refactor versus rebuild, the ROI of revisiting old code, and how AI is (and isn't) changing the equation. This is a must-listen for engineering leaders navigating complex technical decisions in fast-moving environments.

In this episode of Autonomous IT, Live!, Landon Miles hosts leads a three-part discussion focused on spring cleaning your IT systems, workflows, and personal well-being. You'll hear candid, practical insights from IT professionals tackling burnout, technical debt, and infrastructure hygiene head-on.This live show originally aired April 16, 2025  

Russ Mikowski, CEO of SurePeople and longtime revenue leader intech, never planned to become a CEO, until he was recruited to transform a 10-year-old company grappling with technical debt, a scattered ICP, and untapped potential. In this episode of Topline Spotlight, Russ opens up about the tough decisions he's made since taking the helm: rebuilding instead of refactoring, saying "no" to legacy customers, and doubling down on a focused go-to-market strategy for SurePeople's innovative psychometric assessment platform, Prism.You're invited! Join the free Topline Slack channel to connect with 600+ revenue leaders, share insights, and keep the conversation going beyond the podcast!Subscribe to the Topline Newsletter to get the latest industry developments and emerging go-to-market trends delivered to your inbox every Thursday.Tune into The Revenue Leadership Podcast with Kyle Norton every Wednesday. Kyle dives deep into the strategies and tactics that drive success for revenue leaders like Jason Lemkins of SaaStr, Stevie Case of Vanta, and Ron Gabrisko of Databricks.Key Moments:(00:00) Introduction to Topline Spotlight(03:00) Understanding SurePeople and Its Mission(05:51) Russ's Journey to CEO and Company History(08:55) Navigating Technical Debt and Product Development(12:01) Defining Ideal Customer Profile (ICP) and Market Focus(14:50) Company Culture and Communication Strategies(17:53) Inspiration and Leadership Philosophy

Spring is in the air, and it's time to give your IT environment the deep clean it deserves! In this episode of Hands-On IT, host Landon Miles shares nine essential spring cleaning tips to help IT pros declutter, optimize, and future-proof their systems. From cleaning workspaces and dusting off hardware to reviewing patch policies, auditing backups, and addressing tech debt, Landon walks you through practical steps that will boost efficiency, enhance security, and set you up for a smoother year ahead. Tune in and learn how a little proactive maintenance today can save you countless hours of reactive troubleshooting tomorrow!Clean Your Desk and WorkspaceDust Off Your Hardware and Check for WearUntangle and Manage CablesReview Patch PoliciesPurge Old Accounts and Review Software ContractsDeclutter Local Systems and StorageAudit and Test Your BackupsReview Digital and Hardware Tech DebtUpdate Your Documentation and Refresh Policies

In this episode, Dave and Jamison answer these questions: Nearly every time certain developers on the team want to address technical debt, they end up just adding more technical debt. Of course, after one round of addressing technical debt, the developers in question believe that yet another round of redesigning and refactoring is in order. This stresses me out for many reasons, as you can imagine, and has led to my productivity dropping to an abysmal rate. I spend a large chunk my time resolving merge conflicts and re-orienting myself in an ever-changing codebase. Do you have any suggestions for me? Hi! I'm a software engineer at a big tech company, and I'm starting to feel siloed in my IC role. I'm getting my work done, but I'm often lost when it comes to the bigger picture. I can't keep up with what our internal customer teams are doing, what they need, or even what my own team's priorities are. I'm feeling siloed, and it's starting to worry me. I know that just being a good IC isn't enough to advance my career here. To get promoted, I need to understand the impact of my work, be aligned with the team and customer goals, and show that I can contribute to the overall success of the company. But how can I do it? How do I stay informed about customer needs and team priorities and position myself for career growth without getting completely overwhelmed? Thank you for your precious advice!

We're bringing back one of our favorite conversations — and for good reason: Noibu is a trusted partner of Mejuri. In this episode, we revisit our insightful chat with Rohit Nathany, Chief Product and Technology Officer at Mejuri, the leading fine jewelry brand redefining ecommerce. Rohit dives into how his team transitioned from a custom tech stack to Shopify, launched a loyalty-driven mobile app, and built a high-performing internal tech culture that fuels fast, focused innovation. Whether you missed it the first time or just want a fresh take, tune in for sharp insights on balancing speed, scale, and strategy in modern ecommerce.

ABOUT FUNMI OLUDAIYEFunmi is a Managing Director and the Head of the Digital Risk Office for Enterprise Partnerships at Goldman Sachs, where she is pioneering a first-of-its-kind global initiative to embed critical business, security, and engineering risk practices within the engineering organization. With nearly 15 years of experience as a software engineer, architect, and engineering manager, she has a proven track record of leading high-performing teams, delivering innovative technology solutions, and championing best practices in developer experience and productivity across large-scale engineering teams. Most recently, she was the Head of Engineering for Consumer Deposits at Marcus by Goldman Sachs, and prior to that, she led the product engineering teams that built and launched the firm's award-winning credit card partnerships with Apple and later, General Motors. Funmi is a passionate advocate for underrepresented groups in the technology industry and is committed to mentoring the next generation of engineering leaders. Her wealth of experience and dedication to driving positive change make her a sought-after speaker and advisor.ABOUT KETAN GUPTAKetan is a seasoned engineering leader with 13+ years in software development, cloud, architecture, product delivery, and organizational leadership. He excels at building high-performing engineering teams and driving strategic initiatives. As an active community builder, he contributes to the Engineering Leaders Community and champions software craftsmanship.ABOUT SASHA HALLSasha Hall is an Engineering Manager at Planitar Inc, makers of iGUIDE. A University of Waterloo graduate with over 5 years of leadership experience at Pegasus Aeronautics and Deep Trekker, Sasha brings valuable insights on decisive leadership, effective communication, and strategic vision in growing organizations. Their career path through underwater robotics at Deep Trekker, aerial drone systems at Pegasus Aeronautics, and spatial mapping technologies at Planitar showcases a passion for innovative hardware and sensing solutions. This diverse technical background, combined with consistent leadership dedication, has equipped Sasha with a unique perspective on navigating today's complex engineering challenges. Build AI Voice Agents with ElevenLabsElevenLabs is the leading Voice AI platform for developers with thousands of ultra-realistic, human-like voices across 32 languages.Developers use ElevenLabs to build life-like, conversational AI voice agents to handle customer support queries, appointment scheduling, and even offer personalized 1-1 tutoring.Get started for free at elevenlabs.io/elc SHOW NOTES:Funmi discusses why successful eng leaders build true partnerships between engineering & business stakeholders (1:58)Navigating the dynamics of engineering & cross-functional team partnerships (3:00)Creating alignment / building relationships through fostering trust & curiosity (4:42)How engaging w/ curiosity is key to building cross-functional relationships (7:21)Funmi's framework to help identify gaps in understanding (8:56)Recognizing knowledge gaps and relying on subject matter experts (10:15)Tips for navigating partnerships with multiple stakeholders (13:14)What's going on with ELC New York & the power of connecting with eng leaders (14:45)Ketan discusses cloud transformation and AI integration (17:08)Considering challenges w/ security, scalability, cost, flexibility & AI in cloud vs. hybrid migrations (18:04)Explaining the impact of technical debt on organizations (20:04)The STIR framework for managing tech debt during cloud migrations (21:17)Translating tech debt into business value w/ STIR (24:17)Separating continuous improvement / performance from tech debt (27:02)Understanding team strengths & bolstering team motivation (29:24)Ketan's experience with ELC London (31:07)Have fun with decision-making (33:29)Sasha discusses optimizing team processes amid company growth & new hires (35:11)Effective decision-making - balancing being decisive & thoughtful (37:36)Examples of balancing quick decision-making w/ thoughtfulness (39:05)How to refactor repetitive tasks to improve efficiency (40:32)Balancing time, risk & impact in decision-making processes (42:06)The value of building a network & finding mentors outside your own company (45:03)Advice for jumping into ELC community events (47:41)This episode wouldn't have been possible without the help of our incredible production team:Patrick Gallagher - Producer & Co-HostJerry Li - Co-HostNoah Olberding - Associate Producer, Audio & Video Editor https://www.linkedin.com/in/noah-olberding/Dan Overheim - Audio Engineer, Dan's also an avid 3D printer - https://www.bnd3d.com/Ellie Coggins Angus - Copywriter, Check out her other work at https://elliecoggins.com/about/

Wie geht man die Quartals- und Jahresplanung an und balanciert verschiedene Anforderungen?Für viele ist es ein langweiliges und notwendiges Übel. Für andere die beste Zeit des Jahres - Die Quartals- bzw. Jahresplanung. Firmen lieben es zu planen. Firmen lieben es, den Kunden neue Features zu versprechen. Produktmanager können endlich alles in die nächsten 3 Monate einordnen, dann wird das gemacht und die Welt ist wieder in Ordnung.Am Ende des Quartals fragt man sich dann aber: Wieso hat das alles so lange gedauert? Wieso haben wir für Feature X 2 Wochen geplant, aber es wurden 6 Wochen draus? Wieso werden wir bei der Software-Entwicklung langsamer und nicht schneller? Das ist ein bekanntes Bild in vielen Firmen, denn oft findet die Stimme der Software-Entwickler*innen keinen Platz in der Planung.Technical Debt abbauen? Machen wir nächstes Quartal. Was für die eigene Team-Produktivität tun, um manuelle Aufgaben zu automatisieren? Das lohnt sich nicht. Kleine Bugs, sogenannte Papercuts, fixen um die Power-User glücklich zu machen? Zu klein, machen wir nebenher. Software updaten? Das ist Keep The Lights On Arbeit und kann doch Ops machen. So oder so ähnlich trägt es sich alle 3 Monate in Firmen zu.In dieser Episode geben wir euch mal ein paar Leitfragen und ein spezifisches Framework an die Hand, wie man die Software-Entwicklungs-Ressourcen gut über das nächste Quartal balanciert, es genug Features in die Roadmap schaffen, aber auch Zeit für Tech Debt und Produktivitätsverbesserungen bleibt. Dabei klären wir, warum eine gewisse Planung eigentlich so wichtig ist, wer eigentlich immer die ganzen Anforderungen auf den Tisch knallt, was Over-Commitments und Rollovers sind, wie Ubuntu und Github mit Mission Papercut kleine Bugs zu einem großen Projekt gemacht hat aber auch warum eine Quartalsplanung in die Bereiche KTLO, Build New Stuff, Improve Stuff und Productivity eingeteilt werden sollte.Das Thema klingt trocken. Dennoch kann dies euch eine Stimme im Planungsprozess geben, damit ihr endlich mal Zeug aufräumen könnt.Bonus: Ist Jira das neue ERP-System?Unsere aktuellen Werbepartner findest du auf https://engineeringkiosk.dev/partnersDas schnelle Feedback zur Episode:

Kevin Scott is the CTO of Microsoft, where he leads the company's AI and technology strategy at global scale and played a pivotal role in Microsoft's partnership with OpenAI. Prior to Microsoft, Kevin spent six years at Linkedin as SVP of Engineering. Kevin has also enjoyed advisory positions with Pinterest, Box, Code.org and more.  In Today's Episode We Discuss: 04:10 Where is Enduring Value in a World of AI 10:53 Why Scaling Laws are BS 12:26 What is the Bottleneck Today: Data, Compute or Algorithms 15:38: In 10 Years Time: What % of Data Usage will be Synthetic 20:04 How Will AI Agents Evolve Over the Next Five Years 23:34: Deepseek Evalution: Do We Underestimate China 28:34 The Future of Software Development 31:53 The Thing That Most Excites Me in AI is Tech Debt 35:01 Leadership Lessons from Satya Nadella 41:13 Quickfire Round  

On this episode of the Hedge, Eyvonne, Tom, and Russ talk about topics near and dear to every network engineer's heart--documentation, legacy, and tech debt. What should our philosophy of documentation be? What are legacy, end of life, and tech debt, really?

Luca Casanato, member of the Deno core team, delves into the intricacies of debugging applications using Deno and OpenTelemetry. Discover how Deno's native integration with OpenTelemetry enhances application performance monitoring, simplifies instrumentation compared to Node.js, and unlocks new insights for developers! Links https://lcas.dev https://x.com/lcasdev https://github.com/lucacasonato https://mastodon.social/@lcasdev https://www.linkedin.com/in/luca-casonato-15946b156 We want to hear from you! How did you find us? Did you see us on Twitter? In a newsletter? Or maybe we were recommended by a friend? Let us know by sending an email to our producer, Emily, at emily.kochanekketner@logrocket.com (mailto:emily.kochanekketner@logrocket.com), or tweet at us at PodRocketPod (https://twitter.com/PodRocketpod). Follow us. Get free stickers. Follow us on Apple Podcasts, fill out this form (https://podrocket.logrocket.com/get-podrocket-stickers), and we'll send you free PodRocket stickers! What does LogRocket do? LogRocket provides AI-first session replay and analytics that surfaces the UX and technical issues impacting user experiences. Start understand where your users are struggling by trying it for free at [LogRocket.com]. Try LogRocket for free today.(https://logrocket.com/signup/?pdr) Special Guest: Luca Casonato.

Heimir Thor Sverrisson joins Robby to discuss the importance of software architecture in long-term maintainability. With over four decades in the industry, Heimir has witnessed firsthand how poor architectural decisions can set teams up for failure. He shares his experiences mentoring engineers, tackling technical debt, and solving large-scale performance problems—including one bank's misguided attempt to fix system slowness by simply adding more CPUs.Heimir also discusses his work at MojoTech, the value of code reviews in consulting, and his volunteer efforts designing radiation-tolerant software for satellites.Episode Highlights[00:01:12] Why architecture is the foundation of maintainability – Heimir explains why starting with the wrong architecture dooms software projects.[00:02:20] Upfront design vs. agile methodologies – The tension between planning and iterative development.[00:03:33] When architecture becomes the problem – How business pivots can render initial designs obsolete.[00:05:06] The rising demand for rapid software delivery – Why modern projects have less time for deep architectural planning.[00:06:15] Defining technical debt in practical terms – How to clean up code without waiting for permission.[00:09:56] The rewrite that never launched – What happens when a company cancels a multi-million-dollar software project.[00:12:43] How a major bank tackled system slowness the wrong way – Adding CPUs didn't solve their performance problems.[00:15:00] Performance tuning as an ongoing process – Why fixing one bottleneck only reveals the next.[00:22:34] How MojoTech mentors instead of manages – Heimir explains how their consultancy approaches team development.[00:27:54] Building software for space – How AMSAT develops radiation-resistant software for satellites.[00:32:52] Staying relevant after four decades in tech – The power of curiosity in a constantly changing industry.[00:34:26] How AI might (or might not) help maintainable software – Heimir shares his cautious optimism.[00:37:14] Non-technical book recommendation – The Man Who Broke Capitalism and its relevance to the tech industry.Resources & LinksHeimir Thor Sverrisson on LinkedInHeimir's GitHubMojoTechAMSAT – Amateur Radio Satellite OrganizationThe Man Who Broke CapitalismHow to Make Things Faster

Highlights from this week's conversation include:The Return of the Cynical Data Guy (0:14)Risks of SQL Complexity (2:16)Technical Debt in Data (4:34)Data Mesh Critique (6:38)Governance vs. Decentralization (9:55)Never Let a Stakeholder Tell You They Need a Dashboard (12:05)Dashboard vs. Table (13:34)Organizational Dynamics in Data Requests (16:35)AI and Prompt Writing (19:43)Search Techniques and User Behavior (21:20)Discussion on Code Optimization Tools (23:19)Final Thoughts and Takeaways (24:47)The Data Stack Show is a weekly podcast powered by RudderStack, the CDP for developers. Each week we'll talk to data engineers, analysts, and data scientists about their experience around building and maintaining data infrastructure, delivering data and data products, and driving better outcomes across their businesses with data.RudderStack helps businesses make the most out of their customer data while ensuring data privacy and security. To learn more about RudderStack visit rudderstack.com.

This is the 7th episode of season four. I started this season in January of 2024. My intent was to document the process of writing a book. But even though this season is over a year long, there have only been 7 episodes, and that's because I took a 9 month break. I want to talk more about what happened during that break, and how I was derailed from my plans, and how I recovered. The Four Disciplines of Execution [affiliate link] On Writing Well [affiliate link] by William Zinsser Swimming in Tech Debt (my book) Help This Book (book sharing platform) Useful Books Community Transcript

In the latest podcast on the Thomson Reuters Institute (TRI) Insights channel, we discuss tech debt, which may not be the type of debt you're used to from finance, but its implications can be dangerous to law firms and other businesses all the same. In the podcast, TRI's Zach Warren and Bryce Engelland delve into the concept of tech debt and its implications for the legal industry, discussing how tech debt arises from short-term technological decisions and the importance of managing it to avoid long-term costs.

“Looking at the development pace of this area, it's just a question of when generative AI will take over larger parts of software engineering. It's a leadership responsibility to ensure your organization is ready for AI and you are taking the right path.” AI is changing EVERYTHING – including the way we build software. Are you READY for it? In this episode, we dive deep into the impact of AI on the future of work, particularly in the software development space. Join me and André Neubauer as we explore: * The evolution of AI: From early code generation to today's advanced Generative AI and Large Language Models (LLMs). * The rise of Agentic AI: How AI agents are collaborating to automate complex tasks and reshape software development workflows. * The impact on organizations: How companies can leverage AI to boost productivity, foster innovation, and navigate the challenges of this new era. * The future of software teams: Will AI replace developers or empower them? Discover why smaller, leaner, high-performing teams might be the way forward. * Leadership in the age of AI: Essential strategies for leaders to successfully integrate AI into their organizations and address the concerns of their teams. Listen out for: (00:02:11) Career Turning Points (00:07:56) Giving a Talk on “The Role of AI in Future Workplaces” (00:10:30) What Drives the AI Advancements (00:18:54) The Levels of AI Advancement (00:25:01) AI in Software Engineering (00:26:53) Concerns on Tech Debt and Issues (00:31:11) Impact of AI to Organizations (00:34:34) Smaller and Leaner Teams (00:37:15) The Rise of Solopreneurship (00:41:32) Getting People Onboard to AI (00:44:40) Leadership Measures for Adopting AI (00:49:34) 3 Tech Lead Wisdom _____ André Neubauer's Bio For nearly two decades, André Neubauer has shaped Tech & Product and its interface with the business in varied settings, from startups to major corporations. His journey began in software engineering and evolved into technical leadership, a role he's passionately undertaken for the past 15 years. As CTO, he's spearheaded transformative projects and strategies, backed by an academic foundation in informatics and business economics. Always at the forefront of modern leadership practices, he's transformed companies into tech powerhouses. Beyond his role as CTO, he actively mentors tech leaders and consults businesses, guiding them through their tech challenges. Follow Andre: * LinkedIn – linkedin.com/in/andreneubauer * Newsletter – devpg.substack.com _____ Our Sponsors Enjoy an exceptional developer experience with JetBrains. Whatever programming language and technology you use, JetBrains IDEs provide the tools you need to go beyond simple code editing and excel as a developer.Check out FREE coding software options and special offers on jetbrains.com/store/#discounts.Make it happen. With code. Manning Publications is a premier publisher of technical books on computer and software development topics for both experienced developers and new learners alike. Manning prides itself on being independently owned and operated, and for paving the way for innovative initiatives, such as early access book content and protection-free PDF formats that are now industry standard.Get a 40% discount for Tech Lead Journal listeners by using the code techlead24 for all products in all formats. Like this episode?Show notes & transcript: techleadjournal.dev/episodes/202.Follow @techleadjournal on LinkedIn, Twitter, and Instagram.Buy me a coffee or become a patron.

Thomas Mulreid is the VP of Sales at Orium and he was Kailin Noivo's latest guest on Ecommerce Toolbox: Expert Perspectives. Thomas shared his journey from finance through the tech world, and eventually landed at Orium, just at the very moment that the pandemic started to reshape how we work. Now, he's an expert in the changes that are reshaping the world of ecommerce: headless and composable commerce. In this conversation, Thomas reflects on how Orium has helped brands to quickly create tailored digital experiences with cutting-edge composable strategies. They also explore the pivotal role of MACH architecture in building the sort of flexible solutions that can adapt as businesses grow. Tune in to hear practical advice and learn how innovation and best practices are shaping the future of online shopping.

Check out the full episode on https://www.techtables.com/podcast/182/frank-sweeney-beth-neeley Featuring: - Frank Sweeney, CIO, Arizona Department of Child Safety - Beth Neeley, CIO, Arizona Department of Education In this episode, you'll learn: - How Frank Sweeney transformed DCS's Guardian system from 2 releases to 46 successful deployments in 10 months - Why the Arizona Department of Education's $9M school finance payment system succeeded through strategic stakeholder collaboration - How the Department of Education achieved unprecedented financial transparency and reduced technology debt by $500,000 - The power of authentic leadership and being present in driving organizational transformation - Why strategic team placement and a culture of gratitude are critical success factors in public sector IT Timestamps: (00:00) Welcome and Introductions (01:41) Frank's transition strategy: People, process, and culture at DCS (04:52) Beth's journey: Leading the Department of Education transformation (09:06) Building a culture of gratitude and breaking down bureaucratic barriers (14:07) Success story: Department of Education's $9M payment system overhaul (18:54) DCS transformation: From Guardian system challenges to 46 deployments (22:42) Leadership insights: EOS framework and strategic team placement (25:37) Key leadership lessons: The power of being present and authentic • Frank Sweeney: https://www.linkedin.com/in/frank-sweeney-iot/ • Beth Neeley: https://www.linkedin.com/in/elizabeth-neeley-687099222/ Whenever you're ready, there are 4 ways you can connect with TechTables: 1.

Evan Doyle says AI makes tech debt more expensive, Hunter Ng researches the ghost job ad phenomenon, Gavin Anderegg analyzes Bluesky in light of its recent success, Martin Tournoij rants against best practices & Evan Schwartz tells us why he thinks binary vector embeddings are so cool.

Evan Doyle says AI makes tech debt more expensive, Hunter Ng researches the ghost job ad phenomenon, Gavin Anderegg analyzes Bluesky in light of its recent success, Martin Tournoij rants against best practices & Evan Schwartz tells us why he thinks binary vector embeddings are so cool.

Evan Doyle says AI makes tech debt more expensive, Hunter Ng researches the ghost job ad phenomenon, Gavin Anderegg analyzes Bluesky in light of its recent success, Martin Tournoij rants against best practices & Evan Schwartz tells us why he thinks binary vector embeddings are so cool.

Join us as we sit down with Jordan Kaye, the Head of Technology at Belvedere Trading, to unpack the true nature of technical debt and its broader implications. In this episode, we delve into the delicate balance between managing tech debt and delivering business value, the impact of evolving technology on past decisions, and practical ways to enhance efficiency without compromising quality.  Discover how to achieve flexibility and velocity in Agile development, the importance of intentional, business-aligned decisions, and the benefits of high team autonomy. Jordan shares his unique perspectives on quantifying and visualizing technical debt, effective project scoping, and conscious management.  Gain valuable insights into navigating the complex landscape of tech debt and technological evolution.  Don't forget to like, subscribe, and share this insightful conversation with your network. Highlights: 01:29 Defining Technical Debt 04:00 Quantifying and Managing Tech Debt 06:23 Tech Debt in Different Departments 09:06 The Evolution of Technology and Tech Debt 13:04 Balancing Business Needs and Engineering Discretion 13:58 The Challenge of Replicating Success 14:15 Conscious Decision-Making in Engineering 15:12 The Pareto Principle in Engineering 15:54 Empowering Teams with Business Understanding 18:09 Flexibility Over Correctness 19:47 The Art of Balancing Quality and Speed 21:23 Avoiding Premature Problem Solving 24:00 Just-in-Time Scoping Guest:

I've seen a TON of horror stories with tech debt and code migrations. It's estimated that 15% to 60% of every dollar in IT spend goes toward tech debt (that's a big range, I know). Regardless, most of this tech debt will not be paid down without a radical change in how we do things. Might AI be the Hail Mary we need to pay down tech debt? I don't see why not... My works:

My wife and I have been thinking about some new audio equipment. We've been a little unhappy with our Bose soundbar because of the software flakiness and sporadic network connectivity issues. In looking around, I saw a Sonos product, but after reading a bit about the company's recent history, I decided to look elsewhere. Sidebar: if any of you have recommendations that aren't high-end $$$$ audio, let me know. Read the rest of Tech Debt Perils

In this podcast episode, the host interviews Brian Young, Director of Engineering at Grindr, about the concepts of scale and tech debt in the tech industry. Brian shares insights from his career at major companies like Wayfair and Amazon, highlighting the unique challenges each faced with scaling their systems. He explains the CAP theorem and its implications on consistency, availability, and partition tolerance within large-scale applications. The conversation also delves into the balance of art and science required in scaling, the significance of 'YAGNI' in software design, and the necessity of revisiting technical debt. Brian discusses how contextual understanding is vital for addressing tech debt and explores new technologies like AI-assisted coding tools, which may aid in managing tech debt in the future. Highlights: 00:47 Understanding Scale in Tech 02:48 Designing for Scale at Amazon 05:20 Scaling Strategies at Grindr 06:31 The Art and Science of Scaling 09:59 Technical Debt: A Necessary Evil? 17:53 The Role of Context in Software Engineering 20:50 Future of Tech Debt and AI Solutions Guest: Brian Young (he/him) is Director of Engineering at Grindr, the number 1 social network for the LGBTQ+ community. With more than 13 million monthly active users in virtually every country, Grindr has become a fundamental part of the LGBTQ+ community since its launch in 2009. The company continues to expand its ecosystem to enable gay, bi, trans, and queer people to connect, express themselves, and discover the world around them. Brian has spent 25 years in the software industry as an engineer and leader and has worked at large companies, including Amazon and Wayfair, and start-ups. Brian has built high-scale / low-latency distributed systems, microservices, backend solutions, web apps, and mobile apps and worked in almost every tech stack from dcom and dll hell to modern cloud-based microservices. LinkedIn: https://www.linkedin.com/in/briankyoung/ ---- Thank you so much for checking out this episode of The Tech Trek. We would appreciate it if you would take a minute to rate and review us on your favorite podcast player. Want to learn more about us? Head over at https://www.elevano.com Have questions or want to cover specific topics with our future guests? Please message me at https://www.linkedin.com/in/amirbormand (Amir Bormand)

This week we speak with Bill Raduchel, who has served as a high-level executive and strategic adviser for organizations such as Sun Microsystems, AOL Time Warner, Xerox, McGraw-Hill, and the Salvation Army. Over half a century working with systems, software, and networks, he has remained at the forefront of the technology revolution in media, education, and corporate governance including recognition at Sun as CIO of the Year and the top CFO in the computer industry and at AOL as CTO of the year. He holds more than fifty issued patents as well as a PhD in econometrics from Harvard, where he taught for five years with John Kenneth Galbraith. He has been writing software in some form since he turned fifteen years old in 1961. He is also the author of The New Technology State. This book is about society—how it has changed and what technology is enabling us to do to ourselves. [Repeat from April, 2024]For more on Bubble Trouble, including transcripts of the show, visit us online at http://bubbletroublepodcast.comYou can learn more about Richard at https://www.linkedin.com/in/richard-kramer-16306b2/More on Will Page at: https://pivotaleconomics.com(Times below correspond to the episode without considering any inserted advertisements.)The New Technology State: Redefining the Tech and Government Landscape00:00 Welcome to Bubble Trouble: A Skeptical Conversation00:46 A Journey Through Tech and Economics06:23 The Evolution of Technology and Its Impact on Economics08:02 The Writing Process and Insights into Bill's Book11:21 Exploring the New Technology State and Government Challenges17:43 The Intricacies of Tech Talent and Government Staffing19:53 Tech Debt and the Challenges of Modernization25:55 The Global Tech Landscape: Government and Private Sector Dynamics25:55 Wrapping Up Part One and Teasing Part Two25:55 Simplifying UK Government Websites: A Double-Edged Sword25:55 The Dangers of Centralization and Cybersecurity26:10 Big Tech, Government, and the Quest for Regulation27:59 The Talent Gap in Government and Tech Regulation Challenges29:15 Innovative Solutions andthe Power of Decentralization30:15 The Role of Startups in Tech Innovation and Employee Motivation31:59 Google's Management Revolution: Lessons in Innovation34:45 The Complexities of Regulating Big Tech40:05 Navigating the Future of AI and Government Regulation42:19 Economics, Education, and the Future Workforce44:56 Smoke Signals: Warning Signs in Tech and Regulation50:06 Credits Hosted on Acast. See acast.com/privacy for more information.

BONUS: Mastering Product Management in a Remote World, Insights from Tuple's Head of Product, Eli Goodman NOTE: We want to thank the folks at Tuple.app for being so generous with their stories, and supporting the podcast. Visit tuple.app/scrum and share them if you find the app useful! Remember, sharing is caring!   In this episode, Eli Goodman, Head of Product at Tuple, shares insights from his extensive experience in software development and product management. Having transitioned from engineering management to product leadership, Eli reveals the key strategies Tuple uses to develop its remote pair programming service, which is trusted by companies like Figma and Shopify. Tune in to discover how Tuple handles remote team dynamics, customer-driven development, and balances tech debt with client needs, all while maintaining a customer-centric focus. Introduction to Tuple and Why It's Unique Tuple, a remote pair programming service designed by engineers, solves a pain point that its founders, all pairing enthusiasts, experienced firsthand. They were unsatisfied with generic screen-sharing tools that disrupted the flow of coding collaboration. Tuple's product philosophy is about staying "one inch wide, one mile deep" to ensure the tool stays focused on enhancing the pairing experience without getting in the way. "The details matter. Generic screen-sharing tools just don't cut it for productive pairing." Managing a Remote Team at Tuple Managing a distributed team across the U.S. and Europe comes with its challenges. Eli highlights the importance of alignment and ensuring everyone is on the same page, despite working remotely. He emphasizes the role of Product Owners as "connective tissue" and the power of connecting team members with key initiatives. Through personal conversations, Eli uncovers what motivates his team, allowing him to support them without micromanaging. "What makes you proud? What brings you shame? Understanding these emotions helps uncover what drives our team." Ensuring Effective Communication in a Remote Environment Effective communication is the backbone of remote work, and Eli shares some of the practices that have helped Tuple's team stay aligned and collaborative. From using spontaneous pairing sessions to fostering a culture of checking in, Tuple has created a remote work environment where conversations are naturally sparked, and collaboration is effortless. "We have more space in our schedules for spontaneous pairing, which keeps collaboration flowing." Lessons Learned from Pairing Remotely One of the key insights Eli shares is how Tuple has evolved its remote pairing process. In the past, pairing might have felt like a formal meeting, but now it happens more spontaneously. Tuple's app facilitates this by offering the metaphor of a phone call—engineers can call each other at any time, making collaboration easy, especially when someone is deep into a task and needs quick support. "At Tuple, engineers only have three meetings a week, leaving the rest of the time open for pairing and creative work." Pairing Beyond Programming Tasks While pairing is typically associated with programming, Eli explains how Tuple uses pairing for other activities, like design or planning sessions. This practice has extended beyond coding, fostering a culture where team members collaborate on various tasks that benefit from shared perspectives and live problem-solving. "We've expanded pairing beyond coding, using it for activities like design reviews and project planning." Balancing Customer Feedback with Product Vision Responding to customer feedback is vital, but it can also lead to losing focus. Eli explains how Tuple balances this by capturing as much feedback as possible, using tools like Product Board to keep track of customer requests. However, instead of building every requested feature, Eli focuses on synthesizing broader patterns and emotional triggers that align with Tuple's long-term vision. "Focus on discovery as a product person. Understand the emotional context behind customer feedback—that's what drives great products." Tuple's Ideal Customer and Core Value Tuple's ideal customers are teams that value deep collaboration through pair programming. The platform's most important offering is the ability to make remote pairing seamless and intuitive, something traditional tools fail to deliver. "Tuple is built for teams that believe in the power of collaboration and want a tool that enhances their pairing experience, not disrupts it." Roadmapping: How to Prioritize the Right Work in Product Development Looking ahead, Eli shares Tuple's plans to continue investing in quality and lowering the barriers to remote pairing. One exciting potential direction includes creating a "social layer" within the app to help users feel more connected with their teammates. Another idea is incorporating non-human pairing agents that could assist with specific tasks. "We want to see if we can make it feel like you're right there with your teammates, lowering the barriers to start pairing." Recommended Resources Eli recommends The Mom Test by Rob Fitzpatrick, a must-read for anyone working in product management. The book teaches how to talk to customers in a way that gets honest, useful feedback rather than polite responses that don't help improve the product. "I thought caring about people was enough to talk to customers, but The Mom Test taught me what not to do during customer interviews." About Eli Goodman Eli Goodman has been working on software teams for 17 years. He's been a full-stack developer and engineering manager at both large and small companies, including Etsy and Headspace. A few years ago, Eli transitioned to product management and is now the Head of Product at Tuple, a remote pair programming service used by companies such as Figma, Shopify, and many others in the software industry. You can link with Eli Goodman on LinkedIn, or email Eli at Eli@Tuple.app.

Considerations in paying down tech debt, make Rust work on bare metal, ECDSA side-channel in Yubikeys, trade-offs in deploying SSO quickly, and more! Visit https://www.securityweekly.com/asw for all the latest episodes! Show Notes: https://securityweekly.com/asw-298

Considerations in paying down tech debt, make Rust work on bare metal, ECDSA side-channel in Yubikeys, trade-offs in deploying SSO quickly, and more! Show Notes: https://securityweekly.com/asw-298

Considerations in paying down tech debt, make Rust work on bare metal, ECDSA side-channel in Yubikeys, trade-offs in deploying SSO quickly, and more! Visit https://www.securityweekly.com/asw for all the latest episodes! Show Notes: https://securityweekly.com/asw-298

Considerations in paying down tech debt, make Rust work on bare metal, ECDSA side-channel in Yubikeys, trade-offs in deploying SSO quickly, and more! Show Notes: https://securityweekly.com/asw-298

In this podcast episode, we explore critical technical decisions and the concept of technical debt with Brian Moseley, Co-Founder and CTO of Sixfold. Brian discusses his views on balancing short-term goals with long-term ramifications, including real-life examples from his work. The conversation delves into the use of generative AI in insurance underwriting, the importance of context in decision-making, and the challenge of remote work collaboration. Brian stresses the need for documenting reasoning and decisions to avoid future misunderstandings and highlights the role of whiteboard sessions in accelerating productive outcomes. The episode comprehensively discusses making informed and contextually aware technical choices. Highlights: 01:28 Understanding Technical Debt 02:38 Real-World Examples of Technical Debt 05:47 The Importance of Context in Decision Making 08:38 Asynchronous Communication and Documentation 16:30 Challenges of Remote Collaboration ---- Thank you so much for checking out this episode of The Tech Trek. We would appreciate it if you would take a minute to rate and review us on your favorite podcast player. Want to learn more about us? Head over at https://www.elevano.com Have questions or want to cover specific topics with our future guests? Please message me at https://www.linkedin.com/in/amirbormand (Amir Bormand)

July 10, 2024: John Kirkman, VP of Government, Healthcare, and Education at Island joins Drex for the news. They discuss the recent AT&T data leak affecting 110 million customers, highlighting the persistent challenges in data security. How can companies prevent such breaches, and what are the implications for customer trust? They also explore the tension between user experience and robust security measures, particularly the resistance to multi-factor authentication. Is it possible to streamline security without disrupting workflows? Additionally, the conversation touches on the legacy tech debt in healthcare and the importance of modernizing systems. What innovative solutions can be implemented to balance security with efficiency? The episode wraps up with a look at the future of enterprise browsers and their role in enhancing business processes. How can rethinking user interfaces drive productivity and security?Key Points:00:52 John Kirkman from Island01:23 AT&T Data Leak Discussion02:46 MFA and Legacy Systems10:06 Enterprise Browsers and Future TechNews articles:Massive Snowflake-linked attack exposes data on nearly 110M AT&T customersInternet Browsers Are Getting a Makeover for the WorkplaceThis Week Health SubscribeThis Week Health TwitterThis Week Health LinkedinAlex's Lemonade Stand: Foundation for Childhood Cancer Donate

Send us a Text Message.Rachel Stephens is a Senior Analyst at RedMonk, where she covers emerging growth technologies and markets while helping clients understand and contextualize technology adoption trends. In this conversation, we discuss tech debt, layoffs, software development trends, and more.Where to find RachelLinkedIn: https://www.linkedin.com/in/rachelstephens/Twitter: https://twitter.com/rstephensmeRedMonk: https://redmonk.com/rstephens/author/rstephens/Follow, Like, and Subscribe!Podcast: https://www.thecloudgambit.com/YouTube: https://www.youtube.com/@TheCloudGambitLinkedIn: https://www.linkedin.com/company/thecloudgambitTwitter: https://twitter.com/TheCloudGambitTikTok: https://www.tiktok.com/@thecloudgambitShow LinksLessons Learned: https://atlassianblog.wpengine.com/wp-content/uploads/2024/01/lessonslearned.pdfAI, Code Generation: https://stackoverflow.blog/2024/06/10/generative-ai-is-not-going-to-build-your-engineering-team-for-you/Zach Akil: https://www.zackakil.com/

Christian Hammer is a tech optimist and the dynamic CEO of Vala AI, spearheading innovation at the intersection of artificial intelligence and enterprise solutions. With a career spanning decades across global powerhouses like Wayfair, Nike, Appnexus, and Maersk, Christian has consistently been at the forefront of digital transformation, leaving an indelible mark on the tech landscape. In this conversation, we explored his insights into merging artistic creativity with technological innovation, Vala AI's mission to streamline information within businesses, and his optimistic views on future technologies like genetic manipulation and robotics. Key topics include the intersection of art and technology, the future of software development, and the evolution of human-computer interaction. EPISODE LINKS: Christian Hammer LinkedIn: https://www.linkedin.com/in/chammer1/ Christian Hammer Podcast: http://podcast.techtastic.tech/ Christian Hammer Website: https://christianhammer.io/ Christian Hammer Artwork: https://c-hammer.com/ Vala AI: https://vala-ai.com TIMESTAMPS: 00:00:12 Intro and background 00:00:45 Technology and art 00:01:59 The Intersection of Art and Coding 00:05:29 Process of Creating Art vs Coding 00:08:00 Building solutions and value creation 00:09:33 Vala AI Evolution, Tech Debt and Data Dictionary 00:17:31 Vala AI Use Case Scenario 00:20:07 Future of Software Development and AI 00:25:11 Future of Aplication Interaction 00:28:22 Technological Optimism and Future Innovations 00:33:08 Sci-Fi Recommendations 00:34:30 Closing CONNECT: Website: https://hoo.be/elijahmurray YouTube: https://www.youtube.com/@elijahmurray Twitter: https://twitter.com/elijahmurray Instagram: https://www.instagram.com/elijahmurray LinkedIn: https://www.linkedin.com/in/elijahmurray/ Apple Podcasts: https://podcasts.apple.com/us/podcast/the-long-game-w-elijah-murray/ Spotify: https://podcasters.spotify.com/pod/show/elijahmurray RSS: https://anchor.fm/s/3e31c0c/podcast/rss

Are you a tech leader struggling to control tech debt while navigating the rapid advancements in AI? Stride's Head of AI, Dan Mason, is here to help us unravel the complexities of using generative AI to manage and prevent the tech debt spiral.Dan explains that GenAI's effect on tech debt largely depends on how organizations use it. With proper guidance and context, GenAI can improve code quality, but without oversight, it can lead to bad code and increased tech debt.Dan highlights the necessity of providing GenAI with detailed human-level documentation and instructions for teams to achieve better code quality. Also, the benefits of AI tools differ across industries. Cautious industries like banking may see a reduction in tech debt, while fast-moving startups might incur more debt.Consequently, Dan emphasizes the need for tech leaders to have a strategic plan and ensure AI-generated code is thoroughly reviewed to prevent tech debt accumulation and maintain code integrity. He also warns about the potential pitfalls of ignoring GenAI's impact on tech debt.Listen to the full episode to understand how thoughtful integration of AI tools can enhance team capacity and lead to more intelligent decision-making in your organization."The best way to avoid incurring new debt is to be honest about what GenAI can do. You can't plan your workflows around 'GenAI will just do everything.' Find the things that it's good at and figure out which constraints GenAI can loosen for you. " ~ Dan MasonIn This Episode:- The impact of AI on code quality- The role of human language instructions and human oversight- How to determine the right AI strategy and tools- Strategic application of AI in various industries- How to use Stride Conductor to remediate tech debt- The evolution of the relationship between GenAI and tech debt- Best development practices to prevent the tech debt spiral- Consequences of ignoring GenAI's impact on tech debtAnd much more!Connect with Dan Mason : - LinkedIn - https://www.linkedin.com/in/dnmason Connect with Debbie Madden:- Website - https://www.stride.build/- LinkedIn – https://www.linkedin.com/in/debbiemadden1/- LinkedIn - https://www.linkedin.com/company/stride-consulting/

“As a startup, as a scaleup, you often get one chance. If the first impression is something that's slow, doesn't work, is down entirely, people will move on and go find some other way to solve that problem." Tim Cochran and Kennedy Collins are the co-authors of the “Bottlenecks of Scaleups” series published on Martin Fowler's website. In this episode, we explore several key challenges faced by scaleups, such as product-engineering friction, service disruptions, accumulation of tech debt, and onboarding. Tim and Kennedy share their experiences and provide actionable advice on fostering collaboration, creating unified roadmaps, ensuring system reliability, and managing technical debt. They also emphasize the importance of efficient onboarding and developer experience in navigating the complexities of scaling up a startup.   Listen out for: Career Journey - [00:02:02] Definition of a Scaleup - [00:05:29] Bottleneck #1: Friction Between Product and Engineering - [00:08:24] Healthy Product-Engineering Tension - [00:13:36] Unified Product-Engineering Roadmap - [00:18:54] Bottleneck #2: Service Disruptions - [00:22:16] Cross Functional Attributes - [00:27:09] Bottleneck #3: Accumulation of Tech Debt - [00:32:39] Systems Ownership - [00:38:37] Bottleneck #4: Onboarding - [00:41:01] 3 Tech Lead Wisdom - [00:46:35] _____ Tim Cochran's BioTim Cochran is a Principal in Amazon's Software Builder Experience (ASBX) group. He was previously a Technical Director at Thoughtworks. Tim has over 20 years of experience working with both scaleups and enterprises. He advises on technology strategy and making the right technology investments to enable digital transformation goals. He is a vocal advocate for the developer experience and passionate about using data-driven approaches to improve it. Kennedy Collins' BioAt Thoughtworks, he leads product and design for the Central Market of North America. A product manager by trade and a designer by training, he's most interested in creating (and helping others create) useful and valuable things — be it software or organizational structures. He's also a bit of a nerd about strategy, human behavior, health and fitness, productivity, writing, coffee, cocktails, board games, and the history of product management. Follow Tim: LinkedIn – linkedin.com/in/timcochran Follow Kennedy: LinkedIn – linkedin.com/in/kennedycollins Twitter / X – @kennedycollins _____ Our Sponsors Enjoy an exceptional developer experience with JetBrains. Whatever programming language and technology you use, JetBrains IDEs provide the tools you need to go beyond simple code editing and excel as a developer.Check out FREE coding software options and special offers on jetbrains.com/store/#discounts.Make it happen. With code. Manning Publications is a premier publisher of technical books on computer and software development topics for both experienced developers and new learners alike. Manning prides itself on being independently owned and operated, and for paving the way for innovative initiatives, such as early access book content and protection-free PDF formats that are now industry standard.Get a 40% discount for Tech Lead Journal listeners by using the code techlead24 for all products in all formats. Like this episode? Show notes & transcript: techleadjournal.dev/episodes/179. Follow @techleadjournal on LinkedIn, Twitter, and Instagram. Buy me a coffee or become a patron.

In this episode, Jason and Chris chat about their experiences at various RailsConf andRubyConf's. Then, they have deeper discussions on topics like transitioning from SingleTable Inheritance (STI) to delegated types in coding, addressing technical debts inproduct development, and the challenges and strategies of implementing subscriptionand one-time payment models. Additionally, there's a mention of the 2024 Ruby onRails Community Survey at Planet Argon that you can check out now. Hit download nowto hear more!HoneybadgerHoneybadger is an application health monitoring tool built by developers for developers.Disclaimer: This post contains affiliate links. If you make a purchase, I may receive a commission at no extra cost to you.

This episode of the Professional Services Pursuit is a recording from a recent TSIA webinar hosted by John Ragsdale, Distinguished Researcher, Vice President, Technology Ecosystems at TSIA. In it we discuss the hidden costs associated with technical debt—the cumulative consequences of using outdated or overly customized technology— and how it blocks predictable value delivery across the professional services lifecycle. Other topics discussed include:Understanding technical debtThe cost of outdated technology and the impact it has on employee and customer experienceHow to identify technical debt within your organizationStrategies for prioritizing and addressing these challengesHow to leverage AI and other emerging technologies to enhance forecasting, resource management, and decision-making processes Hosted on Acast. See acast.com/privacy for more information.

It's another episode of User Stories and Market Factors as we try to help some Redditors with their questions and look at recent news. Whether it's what to do when you get vague incomplete user stories from a business analyst, prioritizing bugs and tech debt with or with out a product manager's help, or figuring out how to map the architecture of your company's software platforms, we've got some (hopefully) helpful advice. And then we look at some recent changes at Twitter (now X), including a disastrous Find/Replace update and a change to how new users can't really do much without paying Elon first. And then a look at Post.News shutting down and what that says about the current state of the social network landscape, as well as following up on the latest with Apple's antitrust suits in the EU and US. Join the discussion on Reddit: https://www.reddit.com/r/AcceptanceCriteria/ And on the Discord: https://discord.gg/2Tyj8H9MFF The post E026: Can PMs help prioritize tech debt, how to map architectures, and why are Twitter and Facebook still on top? first appeared on Acceptance Criteria.

Should dev teams be able to stop feature development to handle tech debt?

Is tech debt inevitable?

Hey, welcome to another episode of Making Billions, I'm your host, Ryan Miller and today I have my dear friend Michael Fillios.Michael is the author of two private equity books: Tech Debt 2.0 and Tech Equity. He's also the founder and CEO of IT ALLY, a private equity advisory firm that helps you private equity carnivores to unlock unseen value and avoid the unseen liabilities in the companies that you buy and sell. So what this means is that Michael is about to teach you about the new math of private equity, and how to avoid getting left behind when Making Billions in this space. Subscribe on YouTube:https://www.youtube.com/channel/UCTOe79EXLDsROQ0z3YLnu1QQConnect with Ryan Miller:Linkedin: https://www.linkedin.com/in/rcmiller1/Instagram: https://www.instagram.com/makingbillionspodcast/Twitter: https://twitter.com/_MakingBillonsWebsite: https://making-billions.com/[THE GUEST]: Michael is the author of two private equity books: Tech Debt 2.0 and Tech Equity. He's also the founder and CEO of IT ALLY, a private equity advisory firm that helps you private equity carnivores to unlock unseen value and avoid the unseen liabilities in the companies that you buy and sell.[THE HOST]: Ryan is a Venture Capital & Angel investor in technology and energy.Everyday AI: Keep up and get ahead by making AI work for yourCan't keep up with AI? We've got you. Everyday AI helps you keep up and get ahead.Listen on: Apple Podcasts SpotifySupport the showDISCLAIMER: The information in every podcast episode “episode” is provided for general informational purposes only and may not reflect the current law in your jurisdiction. By listening or viewing our episodes, you understand that no information contained in the episodes should be construed as legal or financial advice from the individual author, hosts, or guests, nor is it intended to be a substitute for legal, financial, or tax counsel on any subject matter. No listener of the episodes should act or refrain from acting on the basis of any information included in, or accessible through, the episodes without seeking the appropriate legal or other professional advice on the particular facts and circumstances at issue from a lawyer, finance, tax, or other licensed person in the recipient's state, country, or other appropriate licensing jurisdiction. No part of the show, its guests, host, content, or otherwise should be considered a solicitation for investment in any way. All views expressed in any way by guests are their own opinions and do not necessarily reflect the opinions of the show or its host(s). The host and/or its guests may own some of the assets discussed in this or other episodes, including compensation for advertisements, sponsorships, and/or endorsements. This show is for entertainment purposes only and should not be used as financial, tax, legal, or any advice whatsoever.

This week we speak with Bill Raduchel, who has served as a high-level executive and strategic adviser for organizations such as Sun Microsystems, AOL Time Warner, Xerox, McGraw-Hill, and the Salvation Army. Over half a century working with systems, software, and networks, he has remained at the forefront of the technology revolution in media, education, and corporate governance including recognition at Sun as CIO of the Year and the top CFO in the computer industry and at AOL as CTO of the year. He holds more than fifty issued patents as well as a PhD in econometrics from Harvard, where he taught for five years with John Kenneth Galbraith. He has been writing software in some form since he turned fifteen years old in 1961. He is also the author of The New Technology State. This book is about society—how it has changed and what technology is enabling us to do to ourselves.For more on Bubble Trouble, including transcripts of the show, visit us online at http://bubbletroublepodcast.comYou can learn more about Richard at https://www.linkedin.com/in/richard-kramer-16306b2/More on Will Page at: https://pivotaleconomics.com(Times below correspond to the episode without considering any inserted advertisements.)In this episode of Bubble Trouble, hosts Richard Kramer and Will Page engage in a deep dive conversation with guest Bill Raduchel, exploring his extensive 60-year career transitioning from chemical engineering to economics, and eventually into the tech and media industries. Raduchel discusses his views on conventional wisdom, the evolution of technology, and its implications on economics, suggesting that technology has outpaced neoclassical economic theories due to its scaling properties and the significance of information. He shares insights from his book and experiences, addressing issues like tech debt, government staffing challenges in the face of rapid technological advancements, and the potential impact of AI on the future of software development. The episode covers the dynamic between big tech companies, government regulation, and the inevitable challenges posed by significant shifts towards AI and increased power demands. Raduchel also presents intriguing ideas on innovating government structures and discusses the practicalities of managing a rapidly evolving tech landscape.00:00 Welcome to Bubble Trouble: A Skeptical Conversation00:46 A Journey Through Tech and Economics06:23 The Evolution of Technology and Its Impact on Economics08:02 The Writing Process and Insights into Bill's Book11:21 Exploring the New Technology State and Government Challenges17:43 The Intricacies of Tech Talent and Government Staffing19:53 Tech Debt and the Challenges of Modernization25:55 The Global Tech Landscape: Government and Private Sector Dynamics25:55 Wrapping Up Part One and Teasing Part Two25:55 Simplifying UK Government Websites: A Double-Edged Sword25:55 The Dangers of Centralization and Cybersecurity26:10 Big Tech, Government, and the Quest for Regulation27:59 The Talent Gap in Government and Tech Regulation Challenges29:15 Innovative Solutions andthe Power of Decentralization30:15 The Role of Startups in Tech Innovation and Employee Motivation31:59 Google's Management Revolution: Lessons in Innovation34:45 The Complexities of Regulating Big Tech40:05 Navigating the Future of AI and Government Regulation42:19 Economics, Education, and the Future Workforce44:56 Smoke Signals: Warning Signs in Tech and Regulation50:06 Credits Hosted on Acast. See acast.com/privacy for more information.

This week, host Dan Lines welcomes back Zach Goldberg, CTO and author of the book 'The Startup CTO's Handbook: Essential Skills and Best Practices for High Performing Engineering Teams.' Zach shares insights from his extensive career as a CTO and his journey in writing a book that condenses the wisdom of numerous other influential works into a single, comprehensive guide.We explore the three core sections of his book:Management Fundamentals: Interviewing, Hiring, Performance Management, Budgeting, etc. Technical Leadership Concepts: Developer Experience, Tech Debt, etc. Hard Technology Decisions: Pragmatism, Tech Stack, etc.Zach provides advice for not only CTOs but anyone in a technical leadership position, offering strategies to develop empathy and understanding within technical organizations.Episode Highlights: 1:59 From Startup CTO to Author and Executive Coach3:41 The Origin of Best Practices and Genesis of the Handbook  10:25 Why the Startup CTO's Handbook isn't just for CTOs 13:02 Part 1: Management Fundamentals Beyond Coding24:50 Part 2: Technical Leadership Concepts & Developer Experience30:57 Part 3: Technology Decisions from a Pragmatic PerspectiveShow Notes:The Startup CTO's Handbook: Essential skills and best practices for high performing engineering teamsSupport the show: Subscribe to our Substack Leave us a review Subscribe on YouTube Follow us on Twitter or LinkedIn Offers: Learn about Continuous Merge with gitStream Get your DORA Metrics free forever

Today's guest is Aaron Chamberlain, Senior Medical Director of the Musculoskeletal Clinical Program at Intermountain Health. Intermountain is a US-based not-for-profit healthcare system with over 350 clinics and 30 hospitals in the Intermountain West, located in Salt Lake City, Utah. Aaron joins us on the program today to talk about the biggest challenges facing healthcare leaders when it comes to driving patient access and improved outcomes. In conversation with Emerj Senior Editor Matthew DeMello, Aaron addresses the problem of tech debt and the role that emerging generative AI capabilities can play in ensuring that doctors are spending more time interfacing with patients than in tedious administrative tasks. If you've enjoyed or benefited from some of the insights of this episode, consider leaving us a five-star review on Apple Podcasts, and let us know what you learned, found helpful, or liked most about this show!

Agile Anti-Pattern Review - Budgeting Buckets of Time for Interruptions & Tech Debt Many teams and organizations try to budget buckets of time to address inbound interruptions and or tech debt. Making it time based is a critical error and an even bigger error is trying to break off percentages for people to do specific types of work. We should have an entire sprint each quarter dedicated to tech debt and should address issues and or concerns as they arise. The core team should NOT be interrupted. How to connect with AgileDad: - [website] https://www.agiledad.com/ - [instagram] https://www.instagram.com/agile_coach/ - [facebook] https://www.facebook.com/RealAgileDad/ - [Linkedin] https://www.linkedin.com/in/leehenson/

In this episode, Dave and Jamison answer these questions: “Hi! Love the show, long time listener. So an architect noticed an issue with credentials embedded into request body being logged. I had planned to resolve that, and someone already had done so for another instance. I took a day or two to figure out how to fix it globally, and even tied it into another filtering we did. That would mean one list of sensitive data patterns to maintain – that we already had, and don't need to worry about which context keys to scan in. Scan them all, CPU time is free after all /s I opened this PR, and received no feedback for a day. Another engineer did mention an alternate approach that would resolve this particular case, but I was trying to fix it globally so we didn't have to maintain a list of keys to scan on. Next day he mentioned he made some click ops change that resolved THIS PARTICULAR INSTANCE, meanwhile still not providing any feedback on the PR. This approach is IMO a maintenance burden: keep two different filtering in sync, proactively add keys to strip. High chance of mistakes slipping in over time. So I said OK works with some caveats, and rejected my PR. I can not explain why but this incident tilted me hard. For one thing he essentially grabbed my ticket with no communication and resolved it himself. Then he provided no feedback and went with a different approach without consulting anyone else. Worst of all, he ended up with an (IMO) markedly worse fix that I had already dismissed as being too brittle and likely to miss things in the future. What do? Am I unreasonable to feel undermined and disrespected?” Hi Dave and Jamison, long time listener love the show. I work on a team that is relatively small in size but we own a huge scope including multiple flavors of client-side app and a bunch of backend integrations. We recently launched our product and since then there have been constant fire due to various tech debt that we never fix. Our manager has attempted to ask the team to share the burden of solving these tech debts, but there are only very few that are actually doing it. I can think of many reason why they are not able/willing to take on the task, likely due to other priorities or unfamiliarity with the part of the codebase. Due to my familiarity with various component, I'm usually the one proposing the fix and actually fixing it. I have started to feel this is taking a toll on my own career development because I ended up not having bandwidth to work on those bigger projects/features that have high visibility and good for promotion. I do think solving the tech debt is important work and don't mind doing them. How would you navigate this situation? Thanks for the awesome podcast!

In this episode we continue the mini-series "Backlog psychology."Would you rather have $5 now or $50 next week? The answer to this question, though it seems logically obvious which is better, does not always produce the same response. The required incentive to convince someone to wait tends to follow an exponential curve upward.This is not just true with money, but for any benefit and incentive: monetary, social, emotional, physical, etc.What does this mean for our backlogs? What about our daily habits?