Tag: #neverrewrite

  • The Never Rewrite Podcast, Episode One Hundred Forty: Evolving Past Boomer AI

    The Never Rewrite Podcast, Episode One Hundred Forty: Evolving Past Boomer AI

    AI is great for coding! How is it doing outside of coding? In this episode Isaac and Dustin dig into AI’s impact on legacy system development, team dynamics, and other human factors beyond the code.

    If you’ve been wondering how AI is changing legacy development, this is the episode for you!

    Watch on YouTube or listen to it at Spotify, Apple Podcasts, or your favorite podcast app, and let us know if you have ever been involved in a rewrite. We would love to have you on the show to discuss your experience!

  • The Never Rewrite Podcast, Episode One Hundred Thirty-Nine: A Failure of the Imagination ft. Mark Mandau

    The Never Rewrite Podcast, Episode One Hundred Thirty-Nine: A Failure of the Imagination ft. Mark Mandau

    Are rewrites a failure of the imagination? Are they the inevitable consequence of deferred maintaince? Is it possible a rewrite to succeed in such a way that it validates the choices that led to a rewrite? Mark Mandau rejoins Isaac and me to discuss how managers and leaders look at the question of rewrites.

    If you’ve ever wondered how managers and leadership evaluate rewrites, this is the episode for you!

    Watch on YouTube or listen to it at Spotify, Apple Podcasts, or your favorite podcast app, and let us know if you have ever been involved in a rewrite. We would love to have you on the show to discuss your experience!

  • How I Will Talk You Out Of A Rewrite

    How I Will Talk You Out Of A Rewrite

    If you come to me saying “we need a rewrite”, I will run you through a lot of “why” questions to discover if you actually need a rewrite.  I am basically trying to answer these three questions:

    1. What will the new system do differently?
    2. Why can’t you do that in the current system?
    3. Why can’t you build the new things separately?

    Answering these questions yourself will help you think through whether you really need to rewrite your existing system.

    Let’s examine each more closely.

    What Will The New System Do Differently

    What will be different about the new system?

    For this exercise you have to ignore code quality, bugs, and developer happiness.  Those are all important, but corporate reality hasn’t changed.  The same forces that resulted in low quality code, endless bugs, and developer unhappiness are still there.  A rewrite might get you temporary relief, but over the long term, the same negative forces will be at work on the new system.

    So, what is different about the new system?  The differences could be technical, like a new programming language, framework, or architecture.  Maybe you need to support a new line of business and the existing system can’t stretch to cover the needs.

    Get clear on what will be different, and write it down.  These are your New Things.

    Why Can’t You Do It In The Current System

    Now that you are clear on what New Things you need, why can’t you build the New Things into the existing system?

    We are still putting aside issues like the existing code quality, bugs, and developer happiness.  If those forces are all that is stopping you from doing the new work in the existing system, I have bad news, those forces will wreck the new system as well.  You don’t need new software, you need to change how you write software.  Stop now, while you only have one impossible system to maintain.

    Other than the forces that cause you to write bad software, why you can’t use the current system.  Get clear.  Write it down.  These are your Forcing Functions.

    Why Can’t You Build The New Things Separately?

    At this point we know what the New Things are and we know the Forcing Functions that prevent you from extending the current system.  Why can’t the New Things live alongside the existing system?

    A rewrite requires rewriting all of your existing system.  Building New Things in a new system because of Forcing Functions, only requires building the New Things.  Why can’t you do that?

    By this point office politics are out.  Office politics can’t overcome Forcing Functions.

    Quality and bugs are also out, because there is no existing code to consider.

    Get clear.  Write it down.  This is your Reasoning.

    Now, take your Reasoning, backed by the Forcing Functions, and you have explained how getting the New Things requires a rewrite.  If your Reasoning can convince your coworkers, then I’m sorry, you do actually need a rewrite.  

    If not, it is time to talk about alternatives.

    What Happens After I Talk You Out Of A Rewrite

    Most rewrites are driven by development culture issues, not the software itself.  This brings us back to code quality, bugs, and developer happiness.  A rewrite won’t fix any of those issues.

    The good news is that you can fix all of them without a rewrite.  Even better news is that fixing them will only take about as much effort as you think a rewrite would take.  The bad news is that your culture is pushing against making the fixes.

    Take it one step at a time, and keep delivering.

  • The Never Rewrite Podcast, Episode One Hundred Thirty-Eight: The MVP Worked. Do We Rewrite It To Scale?

    The Never Rewrite Podcast, Episode One Hundred Thirty-Eight: The MVP Worked. Do We Rewrite It To Scale?

    You’ve made an MVP and it can’t handle its own success. Do you rewrite it? And does starting over to build something you know is useful qualify as a rewrite?

    If you’ve ever had code crushed by success, this is the episode for you!

    Watch on YouTube or listen to it at Spotify, Apple Podcasts, or your favorite podcast app, and let us know if you have ever been involved in a rewrite. We would love to have you on the show to discuss your experience!

  • The Never Rewrite Podcast, Episode One Hundred Thirty-Seven: 2025 Year in Review

    The Never Rewrite Podcast, Episode One Hundred Thirty-Seven: 2025 Year in Review

    Navel gazing time, how did Never Rewrite do in 2025? Isaac and I review our goals and accomplishments from the past year and discuss what 2026 has in store.

    If you like year in review episodes, this is the episode for you!

    Watch on YouTube or listen to it at Spotify, Apple Podcasts, or your favorite podcast app, and let us know if you have ever been involved in a rewrite. We would love to have you on the show to discuss your experience!

  • The Never Rewrite Podcast, Episode One Hundred Thirty-Six: Key Questions to Ask When Navigating Your Career

    The Never Rewrite Podcast, Episode One Hundred Thirty-Six: Key Questions to Ask When Navigating Your Career

    Today is a great day to think about your career! Dustin Raie and I can’t tell you what you should do; we can help you ask yourself questions. No matter what stage of you are in, getting the career you want takes effort on your part.

    If you’ve got a career, this is the episode for you!

    Watch on YouTube or listen to it at Spotify, Apple Podcasts, or your favorite podcast app, and let us know if you have ever been involved in a rewrite. We would love to have you on the show to discuss your experience!

  • The Never Rewrite Podcast, Episode One Hundred Thirty-Five: Is Changing an ERP System a Rewrite? ft. Sophia Rosa

    The Never Rewrite Podcast, Episode One Hundred Thirty-Five: Is Changing an ERP System a Rewrite? ft. Sophia Rosa

    For companies that use an ERP, it is one of their core pieces of software. When a business decides to change ERP vendors, is that a rewrite? In this episode, Sophia Rosa, a project and organizational change manager, tackles the question of rewrites and walks us through the complexities of changing an ERP system. We go deep and learn that changing the software is just the obvious part of process.

    If you’ve ever wondered what it would take to change an ERP and have it go well, this is the episode for you!

    Watch on YouTube or listen to it at Spotify, Apple Podcasts, or your favorite podcast app, and let us know if you have ever been involved in a rewrite. We would love to have you on the show to discuss your experience!

  • The Never Rewrite Podcast, Episode One Hundred Thirty-Four: A Stream of Consciousness Chat on AI, Tech, & Layoffs

    The Never Rewrite Podcast, Episode One Hundred Thirty-Four: A Stream of Consciousness Chat on AI, Tech, & Layoffs

    I had to miss this episode, thankfully Thomas Morris was available to fill in with a fun stream-of-consciousness style chat on AI, Tech, and Layoffs.

    If you’ve ever wondered what it would be like if Isaac replaced me as co-host, this is the episode for you!

    Watch on YouTube or listen to it at Spotify, Apple Podcasts, or your favorite podcast app, and let us know if you have ever been involved in a rewrite. We would love to have you on the show to discuss your experience!

  • The Never Rewrite Podcast, Episode One Hundred Thirty-Three: The Consequences of Having Multiple Sources of Truth

    The Never Rewrite Podcast, Episode One Hundred Thirty-Three: The Consequences of Having Multiple Sources of Truth

    It is called the source of truth because it is the single, verifiable, source of truth. But what if you had 2, independent, sources of truth? Would that be twice as truthy? In this humorous episode, Isaac and I discuss a real instance of a market data system with multiple sources of truth.

    If you’ve ever wondered if financial software is written by world class experts, this is the episode for you!

    Watch on YouTube or listen to it at Spotify, Apple Podcasts, or your favorite podcast app, and let us know if you have ever been involved in a rewrite. We would love to have you on the show to discuss your experience!

  • The Never Rewrite Podcast, Episode One Hundred Thirty-Two: A Thankful Thanksgiving Episode

    The Never Rewrite Podcast, Episode One Hundred Thirty-Two: A Thankful Thanksgiving Episode

    Happy Thanksgiving everybody!

    If you want to get into the holiday spirit with some thanks, this is the episode for you!

    Watch on YouTube or listen to it at Spotify, Apple Podcasts, or your favorite podcast app, and let us know if you have ever been involved in a rewrite. We would love to have you on the show to discuss your experience!