In episode 11 of the Never Rewrite podcast, Isaac Askew and I are joined by special guest Thomas Morris to continue our discussion of company culture.
Listen to it at NeverRewrite, Spotify, or Apple Podcasts.
Category: podcast
In episode 11 of the Never Rewrite podcast, Isaac Askew and I discuss the difference between software that satisfies a specification, and software that delivers client satisfaction. They're two distinct problems and we talk through how to reduce the risk of delivering one without the other.
Listen to it at NeverRewrite, Spotify, or Apple Podcasts.
In episode 10 of the Never Rewrite podcast, Isaac Askew and I discuss the phases that most rewrites go through. Rewrites have distinct up and down patterns; if you've never taken the ride the switches can feel sudden and confusing. Isaac and I explain the phases and take some of the mystery out of why rewrites follow the pattern.
Listen to it at NeverRewrite, Spotify, or Apple Podcasts.
Watch on YouTube
In episode 9 of the Never Rewrite podcast, Isaac Askew shares the story of the first SaaS he ever worked on, and how it helped his customers get raided by the FBI.
Listen to it at NeverRewrite, Spotify, or Apple Podcasts.
In Episode 8 of the Never Rewrite podcast, Isaac Askew and I discuss the process of transforming a Service Business into a SaaS with Brian Begy. What happens when a company wants to evolve from using software to run a service business, to offering software for others to run a service business?
We discuss many ways that won't work, and one path that leads to success.
Listen at NeverRewrite, Spotify or Apple Podcasts:
In Episode 6 Isaac and I discuss the How Company Culture Makes Or Breaks Your Team. We talk through the good and bad, the winds of change, and some things you can do to protect or change the team from within.
Available at Never Rewrite, Spotify and Apple Podcasts
In Episode 5 Isaac and I discuss the Perverse Incentives that push new hires, developers and managers to suggest Rewrites over Iterative Improvement.
How perverse are the incentives behind a rewrite? Perverse enough to drive the developers and managers out of the company. If you're an executive, you don't want to miss this one!
Available at Never Rewrite, Spotify and Apple Podcasts
Episode 4 of The NeverRewrite Podcast is available on your favorite podcast apps, or directly at https://www.neverrewrite.com/podcast/episode-four-nozomi
For those of you who like video, we also started a YouTube Channel!
In Episode 4, Isaac and I speak with special guests Nathan Keys and Colleen Grafton about our shared experience on the Nozomi project. In many ways Nozomi was the genesis of this podcast, it's where I first started noticing the Rewrite Pattern, and where Isaac and I met.
Isaac and I discuss the developer's journey from testing ignorance through acceptance. Sometimes rewrites are the inevitable outcome of the vicious cycle where hard to test code results in a codebase with few tests, which makes changes difficult and risky, which limits the value of writing tests, which leads to developers hate testing.
https://www.neverrewrite.com/podcast/episode-three-why-you-hate-testing
In this episode, Isaac and I try to answer the question "What should you do if you Never Rewrite?"
Listen today at https://www.neverrewrite.com/podcast/episode-two-iteratively-replace
Or Subscribe at:
Do you have a problem that requires a rewrite? Can't find another solution? Don't know where to begin?
Contact Isaac and I and we can help talk you through it!