Podcasts about Technical debt

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.

How To Defeat The 3 Most Common Arguments Against Technical DebtI once worked on a project where we weren't able to think about technical debt until five years in.Like many startups, we had to hustle to get off the ground. In those initial years, we didn't have much time or capacity to even think about addressing the debt we accumulated.And did it ever accumulate.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/

Join G Mark Hardy in this eye-opening episode of CISO Tradecraft as he shares a personal story about his dog Shelby's near-fatal experience and the costly lesson it taught him about technical debt. Discover how small overlooked issues in cybersecurity can compound and lead to significant risks and learn actionable steps to tackle technical debt before it turns into a crisis. Pictures of Dog https://drive.google.com/file/d/1nBc9e3bBJVW0BQt5inGryhP3ahBz4XsQ/view?usp=drive_link  https://drive.google.com/file/d/12V_DuwhgNBKgxJL0yqNq9Fopa4dauJfd/view?usp=drive_link Transcripts https://docs.google.com/document/d/1-_X_9RQrurOLKRvbXyMjgbygESsabcCK  Chapters 00:21 Welcome to CISO Tradecraft 00:36 RSAC 2025 Conference Experience 01:22 Shelby's Health Scare 02:08 Understanding Technical Debt 02:41 The Consequences of Technical Debt 04:09 Shelby's Story as a Technical Debt Analogy 09:28 Lessons Learned from Shelby's Story 13:09 Conclusion and Call to Action

In this episode, Tobi chats with Adam Schuck, Senior Engineering Director at Canva, a company that has scaled to over 5,000 employees, 2,000+ engineers, and 230 million MAUs while remaining profitable. Adam shares his journey through startups (including acquisitions by Twitter and Canva) and large tech companies like Google, leading to his current role managing 220 engineers at Canva. They dive deep into the challenges and strategies behind Canva's hypergrowth, including:

Ever been in a meeting where an executive decrees: "Engineering needs to go faster!" without any nuance or understanding of the underlying issues?What a coincidence - so have we!!!Listen or watch as Product Manager Brian Orlando and Enterprise Business Agility Coach Om Patel discuss this common yet problematic demand. Join us as we unmask deeper organizational issues, explore how to respond to this request, and discuss the potential causes, constraints, and solutions.Whether you're in engineering, product management, or leadership, this episode provides practical insights for addressing the "go faster" demand in ways that deliver business value quickly, under budget, and right on-time!#EngineeringLeadership #ProductManagement #AgileTeamsREFERENCESGood Strategy/Bad Strategy, by Richard Rumelt (book)Arguing Agile #185 "What Companies Do Instead of Strategy"Arguing Agile #103 "Challenges to Building Product Roadmaps"Inspired, by Marty Cagan (book)LINKS YouTube: https://www.youtube.com/@arguingagileSpotify: https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Apple: https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596Website: http://arguingagile.com= = = = = = = = = = = =Toronto Is My Beat (Music Sample)By Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

In this episode of the Tyler Tech Podcast, we examine how the evolving tech landscape, AI adoption, and changing organizational demands are reshaping state and local government.Guest host Bob Ragsdale, director of analyst relations at Tyler, sits down with Dustin Haisler, president of e.Republic, for a forward-looking conversation on the trends shaping public sector innovation. Drawing from his insights at the Center for Digital Government's Beyond the Beltway conference, Dustin explores how governments are managing technical debt, building enterprise technology strategies, and adapting to emerging tools and innovations shaping public sector operations.Dustin also discusses how agencies can embrace continuous improvement, foster a culture of innovation, and meet rising expectations from residents. From workforce reskilling to the importance of data governance and enterprise solutions, this episode is full of practical guidance for public sector leaders charting a course through uncertainty.Tune in to hear how IT leaders and mission owners alike can seize this moment to reimagine service delivery — and why there's never been a more exciting time to work in government.This episode also highlights Tyler Connect 2025, our annual conference designed to bring public sector professionals together to empower, collaborate, and imagine. Join us in San Antonio, Texas, from May 11-14, 2025, for product training, networking, and inspiration to help drive your organization forward. Early registration is now open — visit tylertech.com/connect to secure your spot!Blog: Let's Empower, Collaborate, and Imagine at Connect 2025!And learn more about the topics discussed in this episode with these resources:Download: Building a Resilient GovernmentDownload: A Digital Guide to Modernizing the Resident ExperienceDownload: Revolutionizing the Government Workforce With AIDownload: Digital Access and Accessibility in the Resident ExperienceDownload: How to Create a Unified Digital Payment ExperienceBlog: Partnering With Communities to Build ResilienceBlog: Increase Community Resilience With Modern Payment SystemsBlog: How Cloud-Based Solutions Expand Access to State ServicesListen to other episodes of the podcast.Let us know what you think about the Tyler Tech Podcast in this survey!

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:

In this episode of the Tyler Tech Podcast, we explore how cloud technology helps governments build greater resilience, maintain continuity, and adapt to evolving risks.Russell Gainford, chief technology officer at Tyler, joins us to discuss how the cloud delivers the scalability, flexibility, and reliability agencies need to keep critical services running — even in the face of disruption. From cybersecurity threats to natural disasters and unexpected system demands, cloud-based infrastructure empowers governments to respond quickly and recover confidently.Throughout the conversation, Russell shares insights on the limitations of traditional on-premises environments, the growing importance of proactive risk planning, and how cloud solutions help reduce technical debt while improving operational agility. He also offers best practices for building a roadmap to resilience, including how to prioritize critical systems, plan for dependencies, and make smart investments over time.Tune in to learn how modern cloud strategies are helping government agencies strengthen resilience, improve service delivery, and prepare for the unexpected.This episode also highlights Digital Access and Accessibility in the Resident Experience, a new white paper exploring how public sector organizations can remove barriers and create more inclusive digital services. As governments continue to expand digital offerings, ensuring a seamless, user-friendly experience is more important than ever.Download: Digital Access and Accessibility: Creating a Better Resident ExperienceAnd learn more about the topics discussed in this episode with these resources:Download: Building a Resilient GovernmentDownload: A Digital Guide to Modernizing the Resident ExperienceDownload: Cloud-Smart Strategies for IT Infrastructure ModernizationBlog: How Cloud-Based Solutions Expand Access to State ServicesBlog: Using Cloud-Based Solutions to Improve Access in CountiesBlog: The Cloud Experience: Improving Government ServicesBlog: Future-Proofing Government Through Technology ModernizationVideo: Tyler Talks: The Cloud is NowVideo: 30 Years of Data Moved to Cloud in 5 DaysVideo: Increase Efficiency With the CloudPodcast: Cloud Adoption and Understanding the Risks of Legacy SystemsListen to other episodes of the podcast.Let us know what you think about the Tyler Tech Podcast in this survey!

In this episode, Austin speaks with Brennan Watt, VP of Core Engineering at Anza, about the evolution of Solana's validator clients. The conversation centers on Agave, originally developed at Solana Labs and now, by Anza. Brennan offers perspective on the critical role validator clients play in overall network performance, recounting challenges encountered in 2022 and 2023 and the improvements that have shaped the current landscape. They dive deep on topics such as memory allocation optimizations, the development of the Agave scheduler, and the broader movement toward a multi-client ecosystem. 00:00 - Anza's Origin and Early Challenges with Solana 07:47 - Technical Debt and Development Philosophy 12:58 - Scheduler Innovations and Performance Enhancements 18:19 - Modular Codebase and Future Improvements 22:36 - Governance and Protocol Changes 24:50 - CU Limits and Performance 32:08 - Validator Client Collaboration 35:54 - Future Performance Goals 41:25 - Final Thoughts  DISCLAIMER The content herein is provided for educational, informational, and entertainment purposes only, and does not constitute an offer to sell or a solicitation of an offer to buy any securities, options, futures, or other derivatives related to securities in any jurisdiction, nor should not be relied upon as advice to buy, sell or hold any of the foregoing. This content is intended to be general in nature and is not specific to you, the user or anyone else. You should not make any decision, financial, investment, trading or otherwise, based on any of the information presented without undertaking independent due diligence and consultation with a professional advisor. Solana Foundation Foundation and its agents, advisors, council members, officers and employees (the “Foundation Parties”) make no representation or warranties, expressed or implied, as to the accuracy of the information herein and expressly disclaims any and all liability that may be based on such information or any errors or omissions therein. The Foundation Parties shall have no liability whatsoever, under contract, tort, trust or otherwise, to any person arising from or related to the content or any use of the information contained herein by you or any of your representatives. All opinions expressed herein are the speakers' own personal opinions and do not reflect the opinions of any entities.

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  

Evan Phoenix (@evanphx), CEO of Miren, joins Robby to explore the subtle but powerful difference between writing code that works and writing code that explains itself. They discuss the role of clarity in maintainable systems, why splitting a monolith can backfire, and what developers can learn from artists and tradespeople alike.Episode Highlights[00:01:30] What Makes Software Maintainable?Evan defines maintainability as how easily a newcomer can make a change with minimal context.[00:02:30] Why Business Logic Should Be ObviousA discussion on domain knowledge leakage and abstracting rules like “can we sell today?”[00:05:00] Programming 'Mouthfeel' and the Trap of PrefactoringEvan explains why prematurely optimizing for reuse can lead to unnecessary complexity.[00:07:00] When to Extract Logic: The Copy/Paste SignalA practical approach to identifying reusable components by spotting repeated code.[00:08:00] Technical Debt as a Reflection of Cognitive LoadWhy forgetting your own code doesn't automatically mean it's “bad” code.[00:10:30] Testing as Emotional InsuranceHow writing even basic checks can build team confidence—especially when test coverage is weak.[00:13:00] Daily Integration Tests: A Low-Pressure Safety NetUsing nightly integration runs to catch invisible bugs in complex systems.[00:14:00] Confidence > 100% Test CoverageWhy fast feedback loops matter more than aiming for exhaustive tests.[00:20:00] Splitting the Monolith: A Cautionary TaleEvan shares how decoupling apps without decoupling the database created chaos.[00:22:00] Shared Models, Split Repos, and Hidden PitfallsThe unexpected bugs that emerge when two apps maintain duplicate models and validations.[00:23:00] Better Alternatives to Splitting CodebasesHow separate deployments and tooling can mimic team separation without architectural debt.[00:28:00] The Hidden Cost of Diverging Business DomainsWhen apps evolve independently, business logic begins to drift—undermining consistency.[00:29:00] Building Miren and Staying MotivatedHow Evan approaches early-stage product development with curiosity and detachment.[00:36:00] How to Know When Your Open Source Project Is “Done”Reframing “dead” projects as complete—and why stability is often a feature.[01:01:00] Signals for Trusting Open Source DependenciesEvan's mental checklist for evaluating if a library is worth adopting.[01:07:00] The Importance of Hiring Junior DevelopersWhy investing in beginners is crucial for the future of our industry.[01:08:00] Book RecommendationsEvan recommends The Inner Game of Tennis and Snow Crash.Links and ResourcesEvan Phoenix's WebsiteEvan on GitHubEvan on MastodonBook RecommendationsThe Inner Game of Tennis (book)Snow Crash by Neal StephensonThanks 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.

Send us a textIt's AI Friday on the Customer Success Playbook! In this forward-looking finale of our three-part series with Ken Sandy, we explore how artificial intelligence is reshaping product leadership. From discovery and prototyping to ethical decision-making and team collaboration, AI is not just changing the tools—it's changing the very skills product managers need. Whether you're a product leader or part of a cross-functional team, this conversation offers a roadmap for navigating the AI evolution without losing your human touch.Detailed Description: In this must-listen conclusion to our three-part series, Roman Trebon and Kevin Metzger sit down once again with Ken Sandy, author of The Influential Product Manager, to dissect how AI is revolutionizing the way product managers work.Ken kicks things off with a big-picture perspective: AI's impact will be long-term and transformative, but not immediate or magic. Drawing from past technological revolutions, he explains the familiar hype cycle—from inflated expectations to eventual disruption—and positions AI right in the middle of it.But the real gold is in the practical insights. Ken dives into how AI will affect key aspects of product management:Discovery: Use AI to mine customer support data, user behavior, and feedback at scale, unlocking deeper, faster insights.Prototyping: Rapidly build and iterate concepts using AI-driven tools, allowing for early validation (and quick abandonment of bad ideas).Experimentation: Run more robust, scalable tests that bring clarity to customer behavior and optimize solutions in-market.Ken also delivers a reality check: AI is powerful, but it doesn't replace collaboration. The partnership between product, design, engineering, and CX is more essential than ever. He warns against operating in silos or outsourcing ethical judgment to machines. AI may hallucinate; your team still needs to lead.Plus, the group tackles the tricky topic of technical debt, the future of documentation, and why empathy remains a product leader's superpower. This isn't just a conversation about AI—it's a compelling call to reimagine how we solve problems together.If you want to lead with AI rather than be led by it, this episode is your launchpad.Now you can interact with us directly by leaving a voice message at https://www.speakpipe.com/CustomerSuccessPlaybookKeywords:Artificial IntelligenceProduct ManagementCustomer Success PlaybookStrategic InnovationDiscoveryPrototypingExperimentationCross-functional CollaborationTechnical DebtEmpathy in LeadershipCheck out https://funnelstory.ai/ for more details about Funnelstory. You can also check out our full video review of the product on YouTube at https://youtu.be/4jChYZBVz2Y.Please Like, Comment, Share and Subscribe. You can also find the CS Playbook Podcast:YouTube - @CustomerSuccessPlaybookPodcastTwitter - @CS_PlaybookYou can find Kevin at:Metzgerbusiness.com - Kevin's person web siteKevin Metzger on Linked In.You can find Roman at:Roman Trebon on Linked In.

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

Learn more about your ad choices. Visit podcastchoices.com/adchoicesSee Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.

Learn more about your ad choices. Visit podcastchoices.com/adchoices

What if I told you that the man who flew above Disneyland's Tomorrowland in the 1960s wasn't on wires, but strapped to actual jet engines? The remarkable true story of the rocket belt at Disney parks is more fascinating—and bizarre—than you might imagine.Kelly and Pete explore the surprising origins of personal flight technology, beginning with Wendell Moore of Bell Aeronautics, who adapted stabilization jets from Chuck Yeager's sound barrier-breaking X-1 aircraft into a wearable rocket pack. Though limited to just 21 seconds of flight time and powered by 90% pure hydrogen peroxide, these devices captured worldwide imagination, appearing not just at Disneyland and Disney World, but at presidential demonstrations, the 1984 Olympics opening ceremony, and in James Bond's "Thunderball."The rocket belt's journey through entertainment history connects fascinating dots between science fiction and reality. From Buck Rogers' "jumping belt" of 1920s comics to Commando Cody's rocket adventures in 1950s film serials, America had been primed to embrace personal flight long before it became technically possible. When Disney showcased these devices above Tomorrowland, they were fulfilling dreams decades in the making.But this is just the beginning of a story that grows increasingly strange. As competing rocket belt designs emerge, the narrative takes unexpected turns involving lawn-mowing teenagers who became rocket men, alleged drug smuggling operations, baseball bat confrontations, stolen equipment, and the birth of troubling rivalries that will ultimately lead to truly startling consequences.This first installment of a two-part rocket belt saga lifts off from the Flight Circle of yesterday's Tomorrowland and soars through a landscape where Disney history intersects with one of technology's most persistently appealing—yet perpetually impractical—dreams. Join us next time as the story grows even more unbelievable.==================================================================Show Notes: Bill Suitor is his name, not Robert as Kelly says early on.Dr. Theopolis on Buck Rogers was voiced by Howard F. Flynn.It's actually unclear if Tommy Walker booked the Bell Rocketbelt team for the 1964 World's Fair. He did, however, book Suitor to fly the RocketBelt for the 1984 Olympic Games opening as well as the team's 1965 and 1967 appearances at Disneyland.Walker, by the way, also composed the six-note "Charge!" fanfare heard at American sporting events.Astronaut Charles Duke: https://en.wikipedia.org/wiki/Charles_DukeKelly is playing fast and loose with the attraction naming. Rocket to the Moon (1955), Flight to the Moon (1967), Mission to Mars (1975).The Jetbelt guys actually could have launched from the location of the former Flying Saucers ride in 1967 because it had been converted to the Tomorrowland stage.Technical Debt at Disneyland article - https://boardwalktimes.net/the-cost-of-endless-magic-theme-parks-and-technical-debt-73a4bb29bb24Jaxxon!  https://starwars.fandom.com/wiki/Jaxxon_T._TumperakkiThanks for listening!We'd love it if you would give us a cheeky little review on your podcast platform of choice. They're really helpful.Come visit our Facebook group at https://www.facebook.com/groups/1511094196139406 or drop us a note to comments@lowdown-plus-up.com and let us know any questions or comments about how YOU would like to plus-something-up! We are a Boardwalk Times production.Boardwalk Times, https://boardwalktimes.net/Boardwalk Times store, https://boardwalktimes.store .

Not every messy piece of code needs a refactor. Noémi Ványi, Senior Software Engineer at Xata, joins Robby to discuss how to develop the intuition to know when refactoring is truly necessary and when it's just unnecessary churn. She shares her approach to balancing pragmatism and maintainability, how product teams and developers can work better together, and why developer autonomy is key to sustainable software.Drawing from her experience working on both open-source and closed-source projects, Noémi reflects on the unique challenges each presents—whether it's dealing with unresponsive GitHub issue reporters, handling unanticipated user behaviors, or navigating large-scale refactors in existing systems. She also shares her philosophy on technical debt: not all of it needs to be paid down, and some of it can actually be strategic.Robby and Noémi also explore the importance of writing meaningful commit messages, the hidden benefits of reviewing open-source pull requests, and why developers should stop waiting for permission to clean up their codebases.Episode Highlights[00:01:00] The characteristics of well-maintained software: modular design, good tests, and observability.[00:02:00] Open source vs. closed source software: Why communication matters more than you think.[00:04:50] Not all technical debt is worth paying down—how to decide when to refactor.[00:06:20] Developing engineering intuition: How experience shapes decision-making.[00:11:08] Lessons from refactoring a log processing system at Elastic.[00:17:09] Strategies for modernizing legacy systems without unnecessary rewrites.[00:19:52] Why maintainability is a business requirement, not an afterthought.[00:24:03] Should developers ask for permission to clean up code or just do it?[00:27:00] The impact of good commit messages and pull request documentation (GitHub PR Templates).[00:30:00] Are issue templates in open source a helpful guardrail or a barrier?[00:32:00] How to gain autonomy as a developer and advocate for technical improvements.[00:39:00] Noémi's advice: Only fix problems that are actually problems.Resources MentionedNoémi Ványi's WebsiteNoémi Ványi on GitHubElasticGitHub Pull Request TemplatesGitHubBook RecommendationLost in Thought: The Hidden Pleasures of an Intellectual Life by Zena Hitz

In this conversation, Sébastien Rannou and Loïc Titren from Kiln co-host Terence Tsao, Core Ethereum Developer at Offchain Labs. Together, they discuss the upcoming Ethereum upgrade known as Pectra, focusing on its implications for the consensus layer and the development process behind it. Terence shares his journey in Ethereum development, the challenges faced in implementing various EIPs, and the importance of testing in the upgrade process. The discussion also touches on the future of Ethereum, the role of Prysm in the ecosystem, and the anticipated changes with the Beam Chain.RESSOURCES MENTIONED:

Anuj Ojha: Beyond the Iron Triangle, A Path to True Agility Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. Anuj shares his journey of understanding the complexities behind Scrum implementation, particularly when faced with fixed time and scope demands. He emphasizes the importance of learning to communicate effectively with different stakeholders in their own language. Through experience, he discovered that the traditional iron triangle (fixed time, scope, and resources) is a fiction in agile environments. His key insight is that while you can fix two sides of the triangle, attempting to fix all three undermines agility. He suggests building cases for critical needs like technical debt and ensuring all voices are heard when determining what's possible. Self-reflection Question: How do you handle situations where stakeholders demand certainty in all three aspects of the iron triangle? [The Scrum Master Toolbox Podcast Recommends]

Support our work at https://thewpminute.com/supportGet the newsletter at https://thewpminute.com/subscribeTechnical debt is an inevitable challenge for WordPress freelancers who have been in the industry for an extended period. Websites, tools, and services age, while outdated code, incompatible plugins, and inefficient workflows can accumulate. That creates obstacles that hinder progress. The key to success is proactively managing and minimizing technical debt to improve stability and efficiency.Eric Karkovack outlines several strategies for mitigating technical debt, including creating a maintenance plan for websites, monitoring third-party dependencies, and regularly reviewing business tools and processes. By proactively addressing potential issues—such as updating software, selecting reputable service providers, and modernizing workflow systems—freelancers can prevent disruptive surprises and maintain client trust.The goal is to make strategic decisions prioritizing stability while preparing for inevitable technological changes. That ensures a smooth path forward in an ever-evolving technical landscape. ★ Support this podcast ★

In this episode of the Liquid Weekly podcast, host Karl Meisterheim and co-host Taylor Page welcome Paolo Vidale, founder and CEO of Hidden Gears, to discuss the intricacies of technical debt, quality assurance, and the evolution of Shopify development.Paolo shares his journey into development, emphasizing the importance of understanding technical debt both in-house and inherited from previous projects.The conversation delves into the philosophy of quality assurance, the challenges of JavaScript, and innovative approaches like inside-out re-theming to manage technical debt effectively. The episode concludes with insights on the latest changes in the Shopify ecosystem and personal picks from the hosts.Takeaways:• Technical debt is a crucial aspect of development that can accumulate over time.• Quality assurance should be viewed as a philosophy rather than just a task.• Diligence in testing involves anticipating user behavior and potential errors.• Inside-out re-theming allows for gradual improvements without complete overhauls.• JavaScript can introduce complexities, especially with conflicting libraries from apps.• Effective QA processes can prevent surprises and ensure a smoother development experience.• Collaboration with app developers can lead to better product outcomes.• Accessibility testing is an essential part of the QA process.• Understanding the implications of headless architecture is vital for successful implementation.• Using tools like Nacho Nacho can help manage SaaS subscriptions effectively.Timestamps:• 00:00 Introduction and Guest Introduction• 01:15 Paolo's Origin Story in Development• 07:40 Transitioning to Shopify and E-commerce• 09:59 Balancing Marketing and Development• 12:31 Quality Assurance in Development• 17:08 Understanding Quality Assurance• 21:14 Design QA vs. Development QA• 25:06 Accessibility and ADA Testing• 29:19 Navigating Complexity in Design and Accessibility• 30:10 Tools for Accessibility Testing• 33:18 Quality Assurance in Development• 34:32 Diligence and Destruction in QA Testing• 39:23 Understanding Technical Debt• 49:02 Inside-Out Re-theming for Technical Debt• 54:17 JavaScript Challenges and Solutions• 57:13 Dev Changelog and Picks of the WeekFind Paolo Online:• Website: https://www.hiddengears.com• Instagram: https://instagram.com/hiddengears• LinkedIn: https://www.linkedin.com/in/paolovidali/• Twitter(X): https://x.com/paolorobotResources:• ARIA DevTools: https://chromewebstore.google.com/detail/aria-devtools/dneemiigcbbgbdjlcdjjnianlikimpck?hl=en• Browserstack: https://www.browserstack.com/• Deque University: https://dequeuniversity.com/• WAVE: https://wave.webaim.org/• JAWS Inspect: https://www.tpgi.com/arc-platform/jaws-inspect/Dev Changelog:• Removing unnecessary RELEVANCE sort options: https://shopify.dev/changelog/removing-unnecessary-relevance-sort-options• Events and Origins in Store Credit Account Transactions: https://shopify.dev/changelog/events-and-origins-in-store-credit-account-transactions• Attribute Marketing Consent to Retail Locations: https://shopify.dev/changelog/track-the-retail-locations-where-your-customers-update-their-marketing-consentPicks of the Week:• Paolo: Saas and AI Marketplace (https://nachonacho.com/)• Karl: Logseq (https://logseq.com/)• Taylor: Wahl Clipper/Trimmer (https://amzn.to/4keu34q)Signup for Liquid Weekly Newsletter:Don't miss out on expert insights and tips—subscribe to Liquid Weekly for more content like this delivered right to your inbox each week: https://liquidweekly.com/

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.

In this episode, Andy Leonard and Frank La Vigne are thrilled to be joined by Trevor Schulze, the Chief Information Officer at Alteryx. Trevor brings an unparalleled perspective on digital transformation, drawing from his impressive tenure at industry giants such as Micron, Cisco, and RingCentral.Time stamps00:00 "Data Driven: AI & CIO Insights"04:32 CIO's Role in AI Evolution06:50 CIO's Evolving Role with AI11:43 "Embracing Data Democratization"16:24 Democratizing Data Access19:33 "AI Investment and Optimization Cycle"20:55 AI Enhances Tool Configuration Guidance24:42 Breaking Free from Vendor Lock-In27:41 "Unleashing Shadow AI and Technical Debt"31:53 Digital Performance Essential for All Industries34:01 Data Privacy Concerns in AI Use37:30 AI Democratization Challenges for Enterprises42:15 AI Transforming Business Processes43:55 Data-Driven Career Journey47:13 "Building Trust in Data Analytics"52:34 Building Trust in Future Tech

Is your startup struggling to ship new features? Are you constantly putting out fires instead of innovating? You might be drowning in technical debt without even realizing it.In this eye-opening episode, Yaniv Bernstein and Chris Saad demystify the often misunderstood concept of technical debt and its crucial role in startup success.In this episode, you will: Discover what technical debt really is and why it's inevitable for startups Learn to distinguish between good debt that fuels growth and bad debt that strangles innovation Understand how technical debt relates to financial debt and why it matters for your bottom line Explore common types of technical debt and their impact on your business Gain insights into effective strategies for paying back technical debt Master the art of making technical decisions with a business-first mindset Uncover the secret to balancing innovation and technical sustainabilityThe PactHonour The Startup Podcast Pact! If you have listened to TSP and gotten value from it, please: Follow, rate, and review us in your listening app Subscribe to the TSP Mailing List at ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://thestartuppodcast.beehiiv.com/subscribe⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Secure your official TSP merchandise at ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://shop.tsp.show/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Follow us on YouTube at ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.youtube.com/@startup-podcast⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Give us a public shout-out on LinkedIn or anywhere you have a social media following.Key links The Startup Podcast is sponsored by Vanta. Vanta helps businesses get and stay compliant by automating up to 90% of the work for the most in demand compliance frameworks. With over 200 integrations, you can easily monitor and secure the tools your business relies on. For a limited-time offer of US$1,000 off, go to ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠www.vanta.com/tsp⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠. Get your question in for our next Q&A episode: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://forms.gle/NZzgNWVLiFmwvFA2A⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ The Startup Podcast website: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://tsp.show⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Learn more about Chris and YanivWork 1:1 with Chris: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠http://chrissaad.com/advisory/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Follow Chris on Linkedin: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/chrissaad/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Follow Yaniv on Linkedin: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.linkedin.com/in/ybernstein/⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠CreditsEditor: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Justin McArthur⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Content Strategist: Carolina Franco https://www.linkedin.com/in/francocarolina/Intro Voice: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Jeremiah Owyang⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠

Ivett Ördög speaks with host Sam Taggart about rewrite versus refactor -- a choice that many projects face as they grow. It's a topic that inspires a lot of dogmatic feelings. They discuss how companies and projects end up at this crossroads and consider some strategies to try to avoid it. Ivett challenges the myth that you should never rewrite but points to two key factors that need to be present for a successful large-scale rewrite or refactor. They end by talking about how to get management on board for such large-scale rewrite or refactor projects. Brought to you by IEEE Computer Society and IEEE Software magazine.

Episode OverviewMarty Haught joins Robby to discuss the sustainability of open-source projects, the challenges of maintaining RubyGems, and why the metaphor of technical debt may not fully capture how software ages. Instead, he suggests thinking of it as drift—the natural misalignment of software with its evolving purpose over time.They also dig into security challenges in package management, including how Ruby Central worked with Trail of Bits to audit RubyGems. Marty also shares insights on the EU Cyber Resilience Act and how it might affect open-source maintainers worldwide. Finally, they explore how companies can support open-source sustainability through corporate sponsorships and individual contributions.Topics Discussed[00:01:00] The two pillars of maintainable software: good tests and readability.[00:02:40] From Perl to Ruby: How readability changed Marty's approach to programming.[00:07:20] Is technical debt the right metaphor? Why "drift" might be a better fit.[00:11:00] What does it take to maintain RubyGems? Marty's role at Ruby Central.[00:14:00] Security in package management: How RubyGems handles vulnerabilities.[00:16:40] The role of external audits: Partnering with Trail of Bits for security improvements.[00:20:40] EU Cyber Resilience Act: How new regulations might affect open-source projects.[00:26:00] Funding open source: Why corporate sponsorships are becoming essential.[00:33:40] Advocating for technical debt work in teams: How to make a compelling case.[00:38:20] Processes in distributed teams: Balancing structure with flexibility.Key TakeawaysTechnical debt is often misunderstood. The real issue may not be shortcuts taken in the past, but the way software naturally drifts from its original purpose.Security in package management is a growing concern. Open-source ecosystems like RubyGems require continuous investment to remain secure.Open source needs sustainable funding. Relying on volunteers is not a long-term solution—companies need to contribute via corporate sponsorships.Advocating for code improvements requires strategy. Engineers should frame technical debt discussions around business impact, not just code quality.Resources MentionedMarty Haught on LinkedInMarty Haught on TwitterRuby CentralRubyGemsAuditing the Ruby Ecosystem's Central Package Repository – Trail of BitsEU Cyber Resilience Act OverviewWhat the EU's New Software Legislation Means for Developers (GitHub Blog)Ruby Central Open Source Program – Get InvolvedCorporate Sponsors ProgramGive and Take by Adam GrantConnect with MartyLinkedInTwitterBlueSkyThanks to Our Sponsor!Need a smoother way to share your team's inbox? Jelly's got you covered!

Sometimes, less is more. Here's how I pruned my feature backlog from 120 to 15 items.I'll share my decision-making framework; every single rule comes with examples. Time to cut down on the mental load that is having too many "ideas" in your backlog.The blog post: https://thebootstrappedfounder.com/deleting-your-backlog-a-founders-guide-to-feature-pruning/The podcast episode: https://tbf.fm/episodes/373-delete-your-backlogCheck out Podscan to get alerts when you're mentioned on podcasts: 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 podcast, two tech industry veterans reflect and share candid insights from 20 years of navigating the ever-changing world of tech and software development. Join Product Manager Brian Orlando and Enterprise Business Agility Coach Om Patel as they talk strategies for recession-proofing your career, the critical importance of talking to customers, and the role leadership plays in driving organizational success. Come for the positive experiences, but stay for the cringe-worthy tangents - we also explore the all-too-common pitfalls of tech such as confusing utilization with progress, the prevalence of Tayloristic management, and the emotional toll of accruing technical debt. Whether you're at the start of your career or a 20-plus year veteran like us, we'd love to hear if our experiences are similar to your own and we hope you enjoy our discussion on spending 20 years in tech!#TechCareers #LeadershipLessons #ProductManagement #SoftwareDevelopment #AgileReferencesWeapons of Mass Instruction by John Taylor GattoPunished by Rewards by Alfie KohnTurn the Ship Around! by L. David MarquetThe New Economics for Industry, Government, Education by W. Edwards Deming= = = = = = = = = = = =Subscribe on YouTube:https://www.youtube.com/channel/UC8XUSoJPxGPI8EtuUAHOb6g?sub_confirmation=1YouTubehttps://youtu.be/I_LF4QUU-XMApplehttps://podcasts.apple.com/us/podcast/agile-podcast/id1568557596Spotifyhttps://open.spotify.com/show/362QvYORmtZRKAeTAE57v3= = = = = = = = = = = =Toronto Is My Beat (Music Sample)By Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

Episode SummaryIn this episode of Maintainable, Robby sits down with Carola Lilienthal, Software Architect and Managing Director at WPS. Together, they explore the intersection of cognitive science and software architecture, strategies for tackling technical debt, and why simplicity, modularity, and domain knowledge are crucial for maintainability.Carola shares her approach to improving legacy systems, fostering domain-driven development, and introducing sustainable patterns into software design. She also discusses the Modularity Maturity Index (MMI), a tool her team has used to assess and improve over 300 systems.Topics Covered[00:00:43] What makes software maintainable?[00:01:24] The importance of clear structure, modularity, and simplicity in software.[00:02:38] How patterns help reduce complexity and onboard developers faster.[00:04:42] Addressing the challenges of systems with mixed architectural patterns.[00:06:20] Strategies for fostering creativity while maintaining simplicity.[00:07:05] How to guide teams to balance technical experimentation and maintainability.[00:14:03] Practical techniques for documenting architecture and decisions.[00:16:17] What is the Modularity Maturity Index (MMI), and how does it measure system health?[00:18:02] Common mistakes in managing technical debt and how to avoid them.[00:21:20] Why domain knowledge is essential for innovation and problem-solving.[00:33:03] Evolving legacy systems with domain-driven design and transformation.Key TakeawaysModularity matters: Simplified, modular systems with high cohesion and loose coupling reduce cognitive load and technical debt.Patterns as a shared language: Establishing a pattern language within your team creates consistency and eases onboarding.Cognitive science in software: Architecture aligned with how our brains process complexity results in more maintainable systems.Domain knowledge drives innovation: Teams should focus their creativity on solving domain-specific problems, not over-complicating the architecture.The value of architecture documentation: Keeping clear decision records helps teams navigate legacy code and onboard new developers.Resources MentionedCarola's LinkedInWPS WebsiteCarola's books:Sustainable Software ArchitectureDomain-Driven Transformation (English version coming soon)Modularity Maturity Index OverviewBooks Carola recommends:Reinventing Organizations by Frédéric LalouxTeam Topologies by Matthew Skelton and Manuel PaisBe sure to follow Carola on LinkedIn and X.Thanks 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.

In this Risky Bulletin sponsor interview, Travis McPeak, the CEO and founder of Resourcely, explains that companies are now realising they have a ton of cloud-related technical debt because of the success of cloud posture management products. Travis talks about different approaches he has seen to tackle rampant cloud misconfigurations. Show notes

Topics DiscussedThe importance of changeability as a core characteristic of well-maintained software.How GitHub has approached accessibility as a business and legal imperative.The evolution of GitHub's frontend system, spanning over 2,000 pages, and the concept of "frontend vintages."Primer: GitHub's design system and the paradox of its success—consistency vs. changeability.The disproportionate maintenance costs of frontend systems compared to backend systems.Using tools like Axe and keyboard-only tests to identify and resolve accessibility issues.The philosophical balance between creativity and usability in software design.Practical advice for teams starting their accessibility journey with limited resources.How frontend complexity affects scalability, especially in app-like experiences.Joel's advocacy for adopting off-the-shelf components to reduce complexity for smaller teams.Key Takeaways[00:01:12] What Defines Well-Maintained Software?Joel explains how changeability—the confidence to make and deploy changes—provides the foundation for high-quality software.[00:03:05] Accessibility as a PriorityThe Microsoft acquisition drove GitHub's investment in accessibility, introducing SLAs, automated tools, and manual processes to track progress.[00:08:49] Primer: GitHub's Design SystemPrimer fosters consistency but introduces the challenge of making changes across a vast, interconnected system.[00:12:54] The Cost of Frontend ComplexityJoel shares how browser quirks, device diversity, and other variables make frontend maintenance far more expensive than backend systems.[00:28:05] Where to Start with AccessibilityJoel recommends focusing on key user workflows like signing up, making payments, and completing core tasks. He emphasizes the importance of tools like Axe and keyboard-driven tests.Notable Time-Stamps[00:01:12] What Makes Software Well-Maintained? Joel shares how changeability drives quality.[00:03:05] GitHub's Accessibility Journey: The role of SLAs, audits, and automation.[00:08:49] Primer and Design Systems: Balancing consistency with innovation.[00:12:54] The Hidden Costs of Frontend Complexity: Lessons learned at GitHub.[00:20:33] Balancing Creativity with Usability: Joel reflects on the intersection of design and functionality.[00:28:05] Accessibility Best Practices: Where teams should focus their initial efforts.ResourcesJoel Hawksley's WebsitePrimer Design SystemAxe Accessibility ToolsGitHub's ViewComponent FrameworkBook Recommendation:How Buildings Learn by Stewart BrandGuest's LinksJoel Hawksley on GitHubJoel Hawksley's WebsiteThanks 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.

In this episode of the Tyler Tech Podcast, we revisit highlights from some of our most engaging 2024 conversations, focusing on strategies for public sector modernization. From cloud adoption and cybersecurity to AI-driven decision-making and improving accessibility, these discussions explore how digital transformation is shaping the future of public sector innovation.Russell Gainford, Tyler's Chief Cloud Officer, discusses the importance of cloud adoption and avoiding the risks of technical debt in outdated systems. He shares how strategic planning and leadership alignment can ensure modernization success.Sascha Ohler, Vice President of Outdoor Recreation at Tyler, reveals how technology is enhancing state parks, delivering seamless visitor experiences, and making the outdoors more inclusive for all.Rita Reynolds, CIO of the National Association of Counties (NACo), addresses the challenges counties face in workforce recruitment, cybersecurity, and aligning IT strategies to meet modern demands.Vivek Mehta, Vice President and General Manager of Tyler's Platform Solutions Division, explores how artificial intelligence (AI) is enabling governments to boost productivity, enhance decision-making, and improve service delivery while navigating adoption barriers.This episode also celebrates inspiring stories from public sector organizations making a tangible difference in their communities through impactful technology. These examples of innovation highlight the possibilities when purpose-driven solutions meet government needs. For Tyler clients, applications are now open for the Tyler Excellence Awards, which honor organizations driving meaningful change with forward-thinking approaches. Submit your application here. You can also read more about excellence in the public sector below:Blog: Excellence 2024: Data & Transparency SolutionsBlog: Excellence 2024: Connected Community SolutionsAnd learn more about the topics discussed in this episode with these resources:White Paper: Revolutionizing the Government Workforce With AIBlog: Preparing for the Future of AI in GovernmentBlog: Future-Proofing Government Through Technology ModernizationBlog: Key GovTech Trends and Takeaways from 2024 ConferencesBlog: Improving Field Inspections With AITyler Tech Podcast: Cloud Adoption and Understanding the Risks of Legacy SystemsTyler Tech Podcast: AI to Digital Rangers: The Next Era of Outdoor RecreationTyler Tech Podcast: Tech Transformation in CountiesTyler Tech Podcast: The Future of Government with AI and Emerging TechDownload: A Digital Guide to Modernizing the Resident ExperienceDownload: Cloud-Smart Strategies for IT Infrastructure ModernizationListen to other episodes of the Tyler Tech Podcast.Let us know what you think about the Tyler Tech Podcast in this survey!

935: In this episode of Technovation, Peter High speaks with Soumya Seetharam, Chief Digital and Information Officer of Corning, a 170-year-old material science innovator. Soumya discusses her dual role in leading IT operations and driving digital transformation, focusing on reducing technical debt, democratizing technology, and implementing AI-powered solutions like Corning GPT and GenAI operator assistants. Learn how Corning is harnessing data and AI to stay at the forefront of innovation and efficiency.

In this episode of Nova Advisory's CPM Customer Success, host Andy Smetana welcomes back Dave Collins, Director of Solution Consulting and Strategic Alliances at OneStream Software.  Together, they dive deep into a head-to-head comparison of SAP's modular CPM approach and OneStream's unified platform. Learn about the limitations of SAP's fragmented system, including technical debt and integration challenges, and how OneStream eliminates these obstacles with its extensible dimensionality and unified architecture. Discover actionable insights on achieving faster ROI, better financial outcomes, and a seamless transition from legacy systems. Whether you're considering a move or just curious about the landscape, this episode is packed with valuable takeaways for finance leaders. Check out all our episodes here: www.novaadvisory.com/podcast  

I was watching a video called Microservices are Technical Debt. In it, the person being interviewed said that a lot of people really have a distributed monolith. That caught my eye since I've worked with a number of customers who are trying to adopt microservice architectures for their applications. I think this is less a performance/scaling choice than a reworking of their software development teams, and I'm not sure they will end up with a better system. What is a distributed monolith? I am not an expert, but this appears to be a place where all the services still depend on each other. For example, I might have a service getting user profile info that an app calls, with another service getting previous orders, and a third service that returns inventory. In a monolith, if any of these are down, the others don't work. In a distributed monolith, these might be built independently, but perhaps the core app/web page still requires all these to be working to show the user something. Read the rest of Distributed Monoliths

As a product advocate at Nx, Katerina Skroumpelou combines her engineering skills with a knack for connecting with clients. In this episode, she shares how clear documentation, scalable architectures, and a collaborative culture can transform software development for the better.Key Takeaways[00:01:25] Katerina's Background: Robby and Katerina discuss her career journey, starting in engineering and recently moving into product advocacy.[00:02:29] Characteristics of Well-Maintained Software: Katerina highlights key aspects of maintainable software—readability, scalability, and reliability.[00:04:39] Product Advocacy at Nx: Katerina describes her unique role, bridging technical support and customer outreach to ensure clients make the most of Nx tools.[00:07:01] White Glove Approach: The “white glove” service approach allows Katerina to dive deep into clients' codebases, offering a hands-on approach to using Nx effectively.[00:09:52] Scalable Documentation Practices: Balancing clarity and detail, Katerina provides tips on structuring code comments and READMEs to be concise yet thorough.[00:12:09] Managing Technical Debt: Robby and Katerina discuss the importance of keeping code up-to-date and scalable, especially in large systems with high demands.[00:16:00] The Importance of Collaboration: Moving from solo work to team-based code reviews taught Katerina the value of a collaborative approach to maintainable code.[00:19:15] Nx's Monorepo Solution: How Nx provides cache and build tools to optimize mono-repo performance, boosting both speed and organization within projects.[00:22:12] Nx Cloud and CI: Katerina discusses Nx Cloud's role in enhancing CI workflows by allowing parallel tasks and cache sharing across teams.[00:24:07] When to Consider Monorepos: Katerina explains the benefits of monorepos for organizing codebases and improving scalability.[00:26:37] AI Tools in Development: Katerina shares her enthusiasm for new AI tools like StackBlitz's Bolt and their potential to streamline app development.[00:29:00] Finding Motivation at Work: Advice for developers who feel stuck or unmotivated in their current roles and ways to reconnect with the work they enjoy.Resources MentionedNx DevStackBlitz Bolt.newBooks:The Three-Body Problem by Cixin LiuCryptonomicon by Neal StephensonSlaughterhouse-Five by Kurt VonnegutKaterina's social profiles:LinkedInTwitterBlueskyThanks 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.

As product managers and agile practitioners, we often struggle to communicate our value to management in terms they understand.In this episode, you'll learn how to better translate business value to management, make a case for additional resources, and overcome resistance to change in your organization.Join Product Manager Brian Orlando and Enterprise Business Agility Coach Om Patel as we discuss:Translating agile metrics into business valueMaking a case for additional resources in SMBsOvercoming resistance to change in organizationsBalancing new features with technical debt reductionStrategies for demonstrating ROI of agile practices#ProductManagement #AgileLeadership #BusinessValue #OrganizationalChange #TechnicalDebt= = = = = = = = = = = =Watch it on YouTube= = = = = = = = = = = =Subscribe to our YouTube Channel:https://www.youtube.com/channel/UC8XUSoJPxGPI8EtuUAHOb6g?sub_confirmation=1Apple Podcasts:https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596Spotify:https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3= = = = = = = = = = = =Toronto Is My Beat (Music Sample)By Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

Welcome to another engaging episode of the Maintainable Software Podcast! In this episode, Robby sits down with Moriel Schottlender, Principal Software Engineer at the Wikimedia Foundation, to explore the complex journey of modernizing MediaWiki, the software behind Wikipedia. Moriel shares her insights on what it takes to keep an enormous monolithic codebase maintainable while supporting an ever-growing and diverse set of global users. She highlights the importance of modularization, ownership, and the delicate balance between flexibility and stability in open-source software.Key Takeaways[00:00:51] Characteristics of Well-Maintained Software: Moriel discusses the three crucial characteristics of well-maintained software: ownership, modularization, and documentation.[00:01:09] Ownership and Rules for Contribution: Ownership goes beyond just fixing bugs—it involves understanding the architectural purpose and maintaining consistency even as teams change.[00:03:35] Product Vision's Role in Maintainability: Why a clear product vision is essential for maintaining software, even in the face of organic growth.[00:07:14] Balancing Experimentation and Long-Term Planning: Moriel shares insights into how Wikimedia balances rapid experimentation with careful, long-term architectural planning.[00:07:32] The Evolution of MediaWiki: MediaWiki's growth from a small project to the backbone of Wikipedia, now supporting over 900 wikis, and the challenges that come with scaling.[00:14:18] Modernizing a 23-Year-Old Monolith: Robby and Moriel dive into the challenges of modernizing MediaWiki's architecture, including the difficulties of updating a monolithic structure.[00:17:15]Wikitext vs. Markdown: Moriel explains why MediaWiki uses its own Wikitext language instead of Markdown and the unique challenges it presents.[00:22:25] Architectural Flexibility for the Future: The importance of having a flexible architecture that can adapt to the evolving needs of users and technologies.[00:26:04] Technical Debt and Modularization: How Wikimedia approaches technical debt in MediaWiki and prioritizes architectural interventions to improve modularity and maintainability.[00:39:00] Community Contributions to MediaWiki: Strategies for increasing developer contributions and how Wikimedia empowers volunteers while maintaining software quality.[00:41:59] Advice for Aspiring Open Source Contributors: Moriel shares encouraging words for anyone looking to contribute to open-source projects, emphasizing that everyone can make a meaningful impact.[00:35:44] The Role of Documentation: Moriel discusses Wikimedia's efforts to improve documentation and ensure it's useful for both developers and end-users, leveraging the strengths of wiki-based contributions.[00:30:29] Celebrating Small Wins: Moriel talks about how Wikimedia celebrates small victories to keep team morale high in the face of big challenges.Resources MentionedMoriel's WebsiteMoriel on MastodonMediaWiki DocumentationBook Recommendation:Year Zero by Rob ReidConnect with MorielMoriel on LinkedInInstagramTwitterGitHubMastodonThanks 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.

Welcome to another engaging episode of Maintainable! Robby sits down with Kate Holterhoff, Ph.D., a Senior Analyst at RedMonk and former front-end engineer, to explore the intricate world of software maintenance, documentation, and the future of developer roles. Kate brings her unique perspective from her time as a practitioner at a digital marketing agency, her academic background, and her current role in developer advocacy.Topics Explored[00:00:00] Introduction to Kate's Background: Robby and Kate discuss her journey from academia to front-end engineering and now to being a Senior Analyst at RedMonk. Kate shares how her experiences have shaped her perspective on software maintenance.[00:04:00] Well-Maintained Software: Kate dives into her definition of well-maintained software, emphasizing modularity, semantic readability, and the importance of considering future developers who will interact with the code.[00:11:30] The Challenges of Agency Work: Kate reflects on her time at a digital marketing agency, where she often worked on projects that had passed through many hands. She discusses the importance of balancing quick deliverables with maintainability.[00:20:45] The Role of Documentation: Kate shares insights on the value of documentation for distributed teams, highlighting her experience organizing documentation sessions ("documentation paloozas") to capture team knowledge and ensure maintainability.[00:30:00] RedMonk and Developer Advocacy: Kate explains her role at RedMonk and how the firm differs from traditional analyst firms like Gartner. She discusses RedMonk's focus on developers as key decision-makers in the tech landscape.[00:39:15] Front-End Developers as Kingmakers: Robby and Kate explore how front-end engineers are increasingly influencing the adoption of tools and technologies within organizations. Kate describes this trend as front-end developers becoming "kingmakers" in the industry.[00:49:50] AI and Developer Tools: Kate discusses the integration of AI into developer tools, the potential benefits, and challenges for junior developers. She emphasizes the importance of understanding how to read code in an AI-assisted world.Key Takeaways:Emphasize modularity and semantic readability to ensure code can be easily maintained by future developers.Documentation is crucial for maintainability, especially in distributed and contractor-heavy teams.Front-end developers are becoming key decision-makers, influencing tool and technology adoption.AI is increasingly integrated into developer workflows, making it essential for developers to focus on reading and understanding code.The definition of a 'developer' is evolving, with more abstracted tools and AI playing a larger role in development processes.Resources Mentioned:RedMonkKate Holterhoff on LinkedInKate Holterhoff on TwitterDarwin's The Origin of SpeciesEpisode Highlights:[00:00:00] Introduction to Kate's Background[00:04:00] Characteristics of Well-Maintained Software[00:20:45] The Importance of Documentation[00:30:00] What Does a Senior Analyst at RedMonk Do?[00:39:15] Front-End Developers as Kingmakers[00:49:50] The Role of AI in Developer ToolsThanks 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.

Alan Ridlehoover: Building Robust Systems Through Behavior-Centric TestingIn this episode of Maintainable, Robby speaks with Alan Ridlehoover, Senior Engineering Manager at Cisco Meraki. Alan shares his perspective on building well-maintained software by focusing on behavior-centric testing, clear code ownership, and thoughtful technical decisions that stand the test of time.Alan discusses his experience working in both startup environments and large-scale engineering teams, including how he navigates the unique challenges of each. He provides practical advice on managing conditional logic in code, scaling with third-party dependencies, and ensuring that testing strategies remain effective as systems grow in complexity.Key Takeaways:The characteristics of well-maintained software: behavior-centric testing, solid code principles, and ownership boundaries.Balancing the needs of startups vs. large enterprises when it comes to software maintenance.Alan's approach to handling conditional logic with a technique called "rehydration" to simplify complex code.Why focusing on behavior, not implementation, is critical for scalable, maintainable tests.The importance of interfaces and facades for managing third-party dependencies and future scalability.How to approach technical debt as a conscious trade-off, not an inevitable burden.Best practices for addressing flaky tests, including managing non-determinism, order dependencies, and race conditions.How to set up effective monitoring and alerting systems to maintain a healthy software environment.The role of team structure and product ownership in delivering sustainable, high-quality software.Episode Highlights:[00:05:32] Introduction to the Guest's Background: Robby and Alan discuss Alan's work at Cisco Meraki and his approach to well-maintained software.[00:15:10] The Importance of Behavior-Centric Testing: Alan explains why focusing on behavior, not implementation, helps in both startups and large-scale environments.[00:24:30] Rehydration: A Strategy for Managing Conditional Logic in Code: Alan shares his method for simplifying code with many conditionals.[00:35:00] Navigating Technical Debt: Alan offers advice on how to strategically manage technical debt without slowing down business needs.[00:45:18] Monitoring and Alerting: Alan's tips on keeping systems healthy and avoiding customer-facing issues through smart monitoring setups.Resources Mentioned:Radical Candor by Kim ScottThe Code GardenerConnect with Alan Ridlehoover:LinkedInThe Code Gardener Blog 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.

In this episode of the Maintainable Software Podcast, Robby sits down with Saron Yitbarek, founder and CEO of DiscoLink, to explore the challenges of maintaining early-stage software while balancing multiple streams of income. Saron shares her journey from being a solo developer to hiring her first teammate and the lessons learned along the way about code maintainability and business logic.Episode Highlights[00:05:32] Introduction to Saron's Background: Robby and Saron discuss her startup, DiscoLink, and the initial development of its MVP.[00:10:50] The Importance of Context in Code: Saron emphasizes why understanding the business decisions behind code is crucial for maintainability.[00:15:10] Onboarding a New Developer: Saron shares her experience hiring her first developer and how it changed her approach to software maintenance.[00:20:32] Multiple Streams of Income: Saron explains her motivation behind building DiscoLink to help professionals manage different revenue streams.[00:25:40] Transparency Around Money: A candid conversation about developers' fears around charging for their work and how to overcome them.[00:30:45] Ethics and Side Projects: Robby and Saron discuss ethical considerations when working on side projects while employed full-time.[00:35:12] How Podcasting Shaped Saron's Career: Saron talks about how being a podcast host impacted her career growth and networking.Key TakeawaysMaintainability Beyond Code: Saron highlights the importance of documenting not just the code but also the business rationale behind decisions.Onboarding Challenges: Bringing a new developer into a solo-built project requires strong communication, context sharing, and flexible documentation practices.The Power of Multiple Income Streams: Saron's vision with DiscoLink focuses on helping tech professionals build financial security through various revenue channels.Confronting Money Anxiety: Many developers struggle with charging for their work, but transparency and community conversations help break down those barriers.Ethical Side Projects: It's important to consider the ethical implications of using work-learned skills for personal projects.ResourcesSaron Yitbarek on LinkedInSaron Yitbarek on TwitterDiscoLink WebsiteBook Recommendation: Formerly Known as Food by Kristin LawlessLinks:My newsletter: https://themultihyphenate.ck.page/newsletterThanks 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.

Today, we're joined by Rob Wenger, Chief Executive Officer and Co-Founder of Higher Logic, a leading provider of engagement platforms for associations and nonprofits. We talk about:The challenge of knowing when to innovate & at what paceUsing Gen AI to generate revenue & deliver value to users (without going off the rails)Integrating technologies post-acquisitionHow to remediate technical debtAlternatives to real-time integration

In this podcast episode, Amir interviews Addhyan Pandey, Zoro.com's Senior Director of AI and Data. They discuss the role of data platforms in serving businesses, mainly focusing on advanced technologies like machine learning and AI. Addhyan explains Zoro's current AI maturity, the challenges posed by data quality, and the concept of technical debt in data management. He also touches on the importance of self-service and human-in-the-loop systems for enhancing business processes. Addhyan shares his experience at Zoro and provides insights on strategic prioritization and stakeholder engagement in data projects. Highlights: 01:13 AI and Machine Learning at Zoro 03:13 Challenges in Data Quality and Technical Debt 05:45 Balancing Business Needs and Data Feasibility 11:43 Self-Service and Human in the Loop 15:14 Addhyan's Onboarding Experience at Zoro Guest: Addhyan Pandey is the Head of AI and Data at Zoro.com, an e-commerce platform focused on supporting businesses. Before this role, he led Machine Learning and Platform teams at Cars.com and Groupon, addressing diverse marketplace and e-commerce challenges. He also spearheaded the re-platforming of the tech stack at Cars Commerce as part of the Product and Strategy teams. With several research papers and patents in machine learning, Addhyan holds a strong technical background and a degree in electronics and communication engineering. LinkedIn: https://www.linkedin.com/in/addhyan-pandey

IntroductionIn this episode of Maintainable, Robby speaks with Lutz Hühnken, Head of Engineering Excellence at Upvest, about the transformative power of event-driven architecture in software development. Lutz brings his extensive experience to the table, discussing how breaking down complex systems into manageable modules and leveraging event-driven design can lead to more resilient and maintainable software.Topics Discussed[00:05:32] Introduction to Well-Maintained Software: Lutz shares his thoughts on the key characteristics of maintainable software, emphasizing modularity and simplicity.[00:10:24] Challenges with "Magic" in Code: The pitfalls of relying too much on frameworks and ORMs, including examples from Lutz's experience with Hibernate.[00:11:16] Understanding Event-Driven Architecture: Lutz explains the fundamentals of event-driven architecture and its advantages over traditional command-driven approaches.[00:13:50] The Role of Promises in Event-Driven Systems: How clear design-time responsibilities ensure reliability in event-driven communication.[00:15:43] Choreography vs. Orchestration: The debate between these two approaches to managing workflows and why Lutz favors choreography for most systems.[00:17:57] Onboarding Developers in Event-Driven Systems: Tips for effectively integrating new team members into an event-driven architecture.[00:26:52] The Role of Engineering Excellence at Upvest: Lutz discusses his new role and the importance of systems thinking in guiding architectural decisions.[00:34:55] Managing Technical Debt: Lutz offers insights into balancing feature development with addressing technical debt, emphasizing the importance of a healthy investment distribution.Key TakeawaysBreaking down large systems into smaller modules with clear boundaries can significantly enhance maintainability.Event-driven architecture offers a powerful way to decouple system components, making them more resilient and scalable.Developers should be cautious of "magic" in code, such as heavy reliance on ORMs, which can obscure underlying complexities and hinder maintainability.Choreography often provides a more scalable and maintainable approach than orchestration in managing complex workflows.Technical debt should be managed proactively, with regular investments in refactoring and productivity enhancements to maintain long-term software health.Resources MentionedLutz Hühnken's BlogEvent-Driven Architecture by Martin FowlerThe Open Society and Its Enemies by Karl PopperConnect with Lutz HühnkenLinkedInTwitterThanks 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.

In this episode of the Maintainable Software Podcast, Robby is joined by Noel Rappin, Staff Engineer at Chime Financial, and the mind behind the latest edition of the classic Programming Ruby book, affectionately known as the "Pickaxe." Noel delves into the intricate process of modernizing a legacy technical book and the lessons learned along the way.Episode Highlights[00:05:32] A Legacy Revisited: Noel Rappin reflects on the process of updating the Programming Ruby book, navigating the balance between preserving its legacy and making it relevant for today's Ruby community.[00:10:17] The Challenges of Modernizing: Noel discusses the complexities of working on a legacy book, including maintaining a consistent tone, updating technical content, and making strategic decisions about what to include or omit.[00:16:12] Parallels with Legacy Code: Noel shares his insights on the similarities between updating a legacy book and maintaining legacy software, emphasizing the importance of understanding past decisions before making changes.[00:21:00] Curating Ruby's Evolution: How Noel approached the task of deciding which Ruby features and practices to highlight in the new edition, considering the evolution of the Ruby community since the book's last update.[00:27:00] The Ruby Ecosystem as a Legacy System: Exploring the idea that the entire Ruby ecosystem can be seen as a legacy system, shaped by past decisions and community standards.[00:33:47] Advice for Aspiring Technical Authors: Noel offers practical tips for those interested in contributing to or updating legacy technical books, including how to pitch ideas to publishers and navigate the challenges of working on established projects.[00:40:00] Maintaining Relevance: Strategies for keeping both software and technical books up-to-date, including Noel's thoughts on the importance of documentation and regular updates.Key TakeawaysUpdating a legacy technical book requires a deep understanding of the community's current needs and the ability to balance respect for the original work with the necessity of modern relevance.The process of modernizing a book like Programming Ruby shares many similarities with maintaining legacy software, including the importance of understanding past decisions and the challenges of working with outdated practices.Community standards play a crucial role in both software maintenance and technical writing, guiding the evolution of both fields.Noel emphasizes the importance of documentation in legacy projects, whether in software or publishing, as a tool for preserving context and aiding future contributors.Resources MentionedProgramming Ruby 3.3 (5th Edition) - The latest "Pickaxe" book, authored by Noel Rappin. Use promo code maintainablefm2024 to get 35% off the ebook.Chime FinancialMurderbot Diaries by Martha WellsWayfarers series by Becky ChambersRubular - Ruby Regular Expression EditorNoel Rappin's WebsiteNoel Rappin on LinkedInNoel Rappin on TwitterFor more episodes like this, be sure to subscribe to the Maintainable Software Podcast.Thanks 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.

Christian Hammer, founder and CEO of Vala AI, joins Matt Watson on the Startup Hustle podcast to discuss AI for software development and the concept of technical debt. They explore the challenges of bridging the gap between business needs and technology, the different definitions of tech debt, and the importance of keeping up with the rate of change in the industry. Christian shares insights into Vala AI's platform, which aims to provide a holistic view of an organization's tech stack and help identify and address tech debt. Takeaways- Tech debt is the gap between business needs and the technology that supports those needs.- Off-the-shelf software often has inherent tech debt because it is not custom-built for specific use cases.- The rate of change in technology is accelerating, leading to an accumulation of tech debt.- The term 'technical debt' can be misleading and should be replaced with more accurate terminology.- AI in software development is still in its early stages and should be treated as a junior engineer or intern.- Effective communication and understanding between business and technology teams is crucial to address tech debt. Find Startup Hustle Everywhere:https://gigb.co/l/YEh5 This episode is sponsored by Full Scale:https://fullscale.io/ Find out more about Vala AI here:https://www.vala-ai.com/ Learn more about Christian Hammer here:https://www.linkedin.com/in/chammer1/ Sign up for the Startup Hustle newsletter:https://newsletter.startuphustle.xyz/ Sound Bites"Tech debt is the gap between business needs and the technology that supports those needs.""All software that we build over time will eventually be replaced or go away.""The evil technical debt is the one that is brutal and prevents you from doing other things." Chapters00:00 Introduction and Background01:30 The Origin of Vala AI and the Problem of Tech Debt07:27 The Accelerating Rate of Change and Tech Debt Accumulation10:43 The Need for Better Terminology and Definitions14:28 The Role of Effective Communication in Addressing Tech Debt25:06 The Importance of Understanding Business Needs and Possibilities29:14 Vala AI's Platform and Approach to Addressing Tech Debt32:00 The Current State of AI in Software Development36:16 Differentiating Between Software Engineers and Coders37:46 Vala AI's Mission and PodcastSee omnystudio.com/listener for privacy information.

In this episode of the Maintainable Software Podcast, Robby sits down with Cassidy Williams, Developer Advocate at GitHub, to explore the dynamic nature of a tech career, the delicate balance between clever code and maintainability, and the evolving trends in software development.Cassidy begins by discussing what makes software truly maintainable—starting with the ease of onboarding for new developers. She emphasizes the importance of clear documentation and warns against the pitfalls of writing overly clever code that might be difficult to maintain in the future.They then delve into the challenges of joining an existing codebase and managing technical debt. Cassidy shares her experiences, noting how codebases often start pristine but become more cumbersome as projects evolve and pivot.The Importance of Onboarding: Cassidy explains how fast someone can jump in and start working on code as a key indicator of well-maintained software.[00:10:21] Balancing Cleverness and Maintainability: Cassidy elaborates on why writing clever code can be a double-edged sword when it comes to long-term maintainability.[00:16:00] Navigating Career Pivots: Cassidy reflects on her own career journey, likening it to a "career jungle gym" where paths are non-linear and require thoughtful decision-making.[00:18:36] Working at Netlify: Cassidy shares her experience with upgrading a router within an existing codebase, highlighting the importance of collaboration and bringing in external expertise.[00:24:00] Local-First Software: Robby and Cassidy explore the trend of local-first software, emphasizing the benefits of data ownership and the ability to work offline.[00:26:30] Developer Wishlists: Cassidy suggests creating personal and communal wishlists for addressing technical debt, fostering a collaborative approach to maintaining software.[00:31:50] Jumbile - Cassidy's Side Project: Cassidy introduces her word game, Jumbile, detailing its development process and the unique challenges she faced.Cassidy also discusses her love for Brandon Sanderson's books, specifically the Mistborn trilogy, and the importance of owning your data in today's digital landscape.Key Takeaways:Maintainable software allows new developers to quickly contribute, thanks to clear documentation and readable code.Clever code can be a joy to write but may lead to maintenance challenges down the line.A career in tech often resembles a jungle gym, requiring flexibility and thoughtful navigation.Involving open-source maintainers in large codebase changes can provide invaluable insights and streamline the process.Local-first software is gaining traction, offering benefits in data ownership and offline functionality.Resources Mentioned:Cassidy's WebsiteCassidy on LinkedInCassidy on TwitterJumbile - Word GameReact RouterMistborn Trilogy by Brandon SandersonThanks 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! 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.

Topics Discussed:The importance of test coverage and readable code in maintaining software over time.How Ruby's syntax contributes to creating maintainable and human-readable code.Challenges and strategies for integrating external APIs, especially AI-driven ones like OpenAI.Obie's approach to creating robust systems using AI, including the use of guardrails and evals.An overview of Olympia, a platform leveraging AI to manage complex workflows and account interactions.The concept of "multitude of workers" where AI components handle discrete tasks in software.Obie's innovative methods for modifying business logic through natural language instructions.The evolving role of AI in software development, including self-healing data and error handling.A sneak peek into Obie's upcoming book, "Patterns of Application Development Using AI"The future of AI in software development, particularly within the Ruby on Rails community.Obie's thoughts on how AI will reshape our approach to legacy code and technical debt.Key Takeaways:AI can enhance software robustness by handling errors gracefully and dynamically adjusting to changes.Ruby's syntax and culture offer unique advantages for integrating AI into software development.The future of AI in software is not just about replacing code but evolving how we think about programming.Obie's approach to AI is about empowering developers to focus on higher-level tasks by automating routine processes.AI-driven development opens new opportunities for innovation, especially in the Ruby on Rails community.Resources Mentioned:OlympiaObie's LinkedInObie's TwitterObie's Medium BlogPatterns of Application Development Using AIThanks 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! 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.

David Rogers - The Digital Transformation Roadmap Part 2   Mastering Digital Transformation: Insights from David Rogers   In this engaging episode, Aidan sits down with David Rogers, the author of 'The Digital Transformation Roadmap'. They delve into the significant challenges and strategies for digital transformation within organisations. Key topics include overcoming psychological and organisational debt, technical capabilities required for transformation, the importance of suitable technology, retaining key talent, and evolving organisational culture. David also shares insights on governance and iterative funding, emphasising the need for smart shutdowns and resource allocation. The episode is packed with practical examples, including successful digital transformations at Walmart and Netflix. David's profound experience and practical tools make this essential listening for business leaders and innovators.   00:00 Introduction and Welcome 00:13 Understanding Organisational and Technical Debt 02:18 The Importance of Tech Capabilities 03:29 Talent and Culture in Digital Transformation 05:19 Governance in Digital Transformation 08:27 The Role of Teams and Boards 20:00 Smart Shutdowns and Innovation Governance 26:07 The Corporate Innovation Stack 29:34 The Broken Model of Innovation 30:02 Governance Model for Innovation 30:42 Path Three Innovations: Challenges and Management 32:15 Innovation Structures and Strategies 34:12 Skipping Vision and Priorities 35:07 Walmart's Strategic Innovation in Online Grocery 41:24 Four Stages of Validation 49:21 Case Studies: Netflix and Diapers.com 54:37 Conclusion and Final Thoughts   Find David here:   Find Aidan McCullen for Keynotes and Corporate Workshops here:   David Rogers, Aidan McCullen, Digital Transformation, Innovation Governance, Iterative Funding, Corporate Innovation, Organizational Change, Innovation Strategy, Technical Debt, Psychological Debt, Innovation Boards, Startup Culture, Agile Methodology, Product Validation, Strategic Priorities, Business Validation, Smart Shutdowns, Innovation Stack, Customer Validation, Executive Insights  

Tom Hearn, VP, Architecture at Insight   In the world of M&A, understanding and managing technical debt is crucial for seamless technology integration.    In this episode of the M&A Science Podcast, we'll explore the concept of technical debt, its impact on IT infrastructure, and strategies for better integration with Tom Hearn, VP, Architecture at Insight.   Things you will learn in this episode: • Technology Integration • AI and machine learning • ERP migration • Synergy assumptions • Working with Insight ****************** This episode is sponsored by DealRoom. Ready to take your M&A to the next level with software made to manage each stage of the deal process? See how DealRoom can facilitate your next deal at https://dealroom.net ****************** Episode Timestamps 00:00 Intro 04:06 Approaching technical and security integration 10:54 Technology Integration 17:17 AI and machine learning 21:00 ERP migration 25:19 Synergy assumptions 35:25 Working with Insight 37:00 Due diligence 40:05 Managing costs 46:29 Return on investment 49:18 Craziest Thing in M&A