Sherman On Software Latest

  • The Never Rewrite Podcast, Episode Forty, Convincing Emotionally-Committed Colleagues That A Rewrite Is Not Worth It

    The Never Rewrite Podcast, Episode Forty, Convincing Emotionally-Committed Colleagues That A Rewrite Is Not Worth It

    Isaac and Jeffrey provide strategies for working with colleagues who are emotionally committed to rewriting old and flawed code at their companies.

    Takeaways:

    • Validate the analysis and perspective of coworkers who are emotionally committed to doing a rewrite.
    • Consider the financial implications of a rewrite and align priorities with the business’s goals.
    • Communicate the rationale for not pursuing a rewrite and document the reasons for future reference.

    Watch on YouTube or listen to it at NeverRewrite, Spotify, Apple Podcasts, or Amazon Music, 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!

  • Net Dollar Retention For SaaS Developers

    Net Dollar Retention For SaaS Developers

    Net Dollar Retention (NDR) is one of the core financial metrics for SaaS companies, and one where software developers have an outsized impact.  This article explains NDR and how software influences can drive the number down.  Finally, it discusses three areas for developers to focus on in order to bring the number up.  

    What is Net Dollar Retention?

    Net Dollar Retention is the rate that your existing customers continue to spend money with your company.  Renewals are flat, churn makes it go down, and expansion makes it go up.

    As a formula using AAR (Annual Recurring Revenue), it looks like this:

    ( [Renewed AAR] + [Expanded AAR] – [Churn] ) / [Previous AAR]

    Besides being a core metric, NDR is a key metric for companies considering going public.  Typically, a company going public needs an NDR over 107%, and ideally over 120%.

    Only existing customers affect this metric!  For Net Dollar Retention it doesn’t matter if you replace every customer that churns with ten new ones, your retention rate will be terrible.

    How Developers Impact Net Dollar Retention

    There are only two real levers with NDR: Increase spend and reduce churn; and there is little that developers can do that will directly increase customer spend.  

    The top 3 developer levers to reduce churn:

    1. Fix any bugs that corrupt or lose data
    2. Make the system more reliable
    3. Make the system faster

    Fix Any Bugs That Corrupt Or Lose Data

    This is the big one!

    Customers come to your service to get things done.  The more often they hit bugs, the faster they will churn.  Only developers can fix bugs and prevent data corruption.

    Make The System More Reliable

    Close second to data corruption is reliability.

    95% success rates mean that you should expect a daily job will fail at least once a month.  If customers don’t trust your system to work, they will sit and watch the process.  Usually by continually hitting refresh on your site.  This is a massive waste for your customer and makes your SaaS much more expensive.

    The less reliable your service is, the faster they will churn.  Reliability is more than just a developer problem, but developers will need to lead the architectural charge.

    Make The System Faster

    Speed is a distant third because it rarely impacts the value that customers get from your service.  Speed, especially UI speed, has a massive impact on the customer experience.

    Slow websites won’t make customers leave, but they will kill your net promoter score and leave them open to a switch.

    They don’t want to waste time staring at a blank screen waiting to render.  When the problem is inefficient code, it is something that only a developer can fix

    NDR is a Core Metric for SaaS Health

    NDR is a core metric for health, and a critical one for companies seriously looking at going public.  Developers can heavily influence the number by reducing churn.

    Fix bugs, improve stability and increase performance.

    Developers can push these levers and improve NDR; no one else in the company has that power!  Become a hero to your business, pay attention to NDR and how you can reduce churn!

  • The Never Rewrite Podcast, Episode Thirty-Nine, Project Risk with Jonathan Stark

    The Never Rewrite Podcast, Episode Thirty-Nine, Project Risk with Jonathan Stark

    Jonathan Stark joins as a guest to discuss the risks of hourly billing and the parallels between risk in a rewrite and in hourly billing. He explains how hourly billing puts all the risk on the client and leads to stressful relationships and arguments about hours and costs.

    Jonathan emphasizes the importance of trust and how it can be built through delivering on promises and becoming an authority in your field. He also provides strategies for pushing back against rewrites and making informed decisions based on cost and quality.

    In this conversation, Jonathan and Jeffrey discuss the importance of taking risks and understanding the business side of software development. They emphasize the need for developers to consider the financial risks their clients are taking on and the value they provide. They also highlight the benefits of speaking in terms of dollars and business outcomes rather than technical details.

    Watch on YouTube or listen to it at NeverRewrite, Spotify, Apple Podcasts, or Amazon Music, 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!

  • Reduce Long Term Customer Churn From Data Growth

    Reduce Long Term Customer Churn From Data Growth

    Customer Relations are ever growing, a CRM must provide Management as well.  Punishing customers for loyalty is the inevitable consequence of not acknowledging and preparing for a long term relationship with your customers.  Destroying your customer’s long term experience increases churn and kills your net-dollar retention.

    Saving long term customers requires work and planning from the frontend to the persistence layer.

    Here is one strategy for each layer to help get you started:

    1. Frontend: Dashboards over pagination.
    2. Backend: Historical limits by default.  
    3. Persistence: Data partitioning.  

    Dashboards Over Pagination

    New customers can see all of their contacts on one page.  Same for their marketing campaigns, tags, and deals.  That changes very quickly for customers who are using your system.  When customers can’t see all of their data on a single page, the solution isn’t pagination, you need dashboards.

    When your customers go to their contacts, you could show them “Page 1 of 10”, or you could show them a dashboard with contact activity.  New contact counts, engagement rates, contacts who need a follow up.

    A pagination is about databases, it is a terrible interface for getting things done.  Make your CRM about management and workflows with dashboards.

    Historic Limits By Default

    Add sensible defaults to everything to limit the amount of data searched.  Default to showing the last 6 months or 1 year of a customer’s interactions.  Keep the older data accessible, but don’t waste the user’s time loading history.

    Put another way, how many extra seconds should you make customers wait to find out if a contact opened an email 3 years ago?  The correct answer is 0 seconds, and also 0 milliseconds; update your APIs accordingly.

    Data partitioning

    Event logs keep track of every email open, click, and website visit.  Because events rarely get deleted, these tables grow and grow with your customers.  Over time, the amount of data in the tables will cause queries to become slow.  The more successful your customers get, the worse your database problems become!

    Partitioning directs the database to create different logical tables based on a key while presenting a view of the combined table.  Events are date based making them great candidates for partitioning by month or year.  The previous tip, Historic Limits By Default, places an upper bound on the data in a table scan.

    Conclusion

    Customer data accumulates over time, especially in CRMs.  Keeping customers for years requires preventing your system from punishing them for accumulating data.  Failing to address the problems will destroy the customer’s experience, increase churn, and reduce your net-dollar retention.

    These three strategies will help you start thinking about data accumulation and how customer needs change over time.  Don’t throw away your loyal customers because your systems only consider the new user experience!

  • The Never Rewrite Podcast, Episode Thirty-Eight, Maintenance Work as a Flight to Safety

    The Never Rewrite Podcast, Episode Thirty-Eight, Maintenance Work as a Flight to Safety

    Isaac and Jeffrey explore the significance of maintenance work for developers, stressing its strategic value during uncertain periods like layoffs. They share personal experiences, highlighting how tackling these tasks can lead to trust, new opportunities, and a more impactful role within a team.

    Watch on YouTube or listen to it at NeverRewrite, Spotify, Apple Podcasts, or Amazon Music, 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 Thirty-Seven, Interview Insights – Changing the Game for Interviewers and Candidates

    The Never Rewrite Podcast, Episode Thirty-Seven, Interview Insights – Changing the Game for Interviewers and Candidates

    Isaac and Jeffrey dissect the flaws in the interviewing process and offer valuable insights for both interviewers and interviewees. They discuss the broken aspects of traditional interviews, highlight the importance of resume tailoring, and share anecdotes about handling past job experiences during interviews. The episode serves as a guide for interviewers to improve the hiring process and for candidates to enhance their chances by navigating the pitfalls and maximizing opportunities.

    Watch on YouTube or listen to it at NeverRewrite, Spotify, Apple Podcasts, or Amazon Music, 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 Thirty-Six, Becoming an Expert in your Company’s Business

    The Never Rewrite Podcast, Episode Thirty-Six, Becoming an Expert in your Company’s Business

    Jeffrey and Isaac discuss why understanding how your company makes money can help you build products that solve the right problems.

    Watch on YouTube or listen to it at NeverRewrite, Spotify, Apple Podcasts, or Amazon Music, 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!

  • Phase 1 is a Millstone not a Milestone

    Phase 1 is a Millstone not a Milestone

    Metaphorically, milestones are markers on your transformation from one state to another.  Millstones are useless, heavy, burdens that you can’t put down.

    Project plans that seek to set out project milestones often end up burdening themselves with millstones.  The mistake is confusing the transformation with the project.  Millstones track the journey, milestones track the destination.

    Things like “Phase 1” can’t be a milestone because there is no guarantee that completing Phase 1 means that you’ve made any progress towards your goal.  Yes, you worked hard and delivered a lot of code.  You’ve done the things you said you would do when you originally planned the project.  Can you objectively show that you’re closer to your destination?

    Milestones, by contrast, are objective, external, measures of progress.  “Customers can use a feature” is a milestone.  “First paying customer” is a milestone.  They are points you expect to cross during the transformation because they demonstrate progress.  You can declare that some milestones are irrelevant, you can set new milestones, but you can’t move the milestones themselves.

    Project based millstones like Phase 1 encourage movement and gaming to meet artificial deadlines.  Can’t complete a feature in time, just move it to Phase 2 and keep the project on track.  Phase 1 encourages wasteful death marches so that developers and project managers can report that the project is moving forward.

    You can put down your millstones wherever and whenever you want.  Makes no difference to anyone or anything other than the artificial constraints you put on your project.  Today is a great time to let go of the weight.

  • The Never Rewrite Podcast, Episode Thirty-Five, The Subtle Art of Refusing Meetings

    The Never Rewrite Podcast, Episode Thirty-Five, The Subtle Art of Refusing Meetings

    Jeffrey and Isaac discuss methods to clear out your recurring meetings and protect your time as new meetings get added to your calendar.

    Watch on YouTube or listen to it at NeverRewrite, Spotify, Apple Podcasts, or Amazon Music, 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!

  • ShermanOnSoftware 2023 Year In Review

    ShermanOnSoftware 2023 Year In Review

    It’s the time of year to look back, reflect, and highlight some interesting pieces you might have missed.

    Also known as the self indulgent year in review post!

    By The Numbers

    In 2022 I set a personal goal of publishing twice a week, or at least 100 articles in 2023.  I published 65 different pieces, almost ⅔ of my goal!

    I published 34 Podcasts, 31 Articles, and wrote over 11,000 words.

    For 2024 I’m going to stretch further and shoot for 50 podcasts and 100 articles; for a combined schedule of 3 items/week.

    I’m also aiming for 6 published articles on other sites and 1 conference talk.

    Top 3 Articles Written in 2023

    Top 3 Most Popular Articles in 2023

    Thanks for reading!