Software Delivery Notebook

Episodes

  • The changing state of Platform Engineering

    The changing state of Platform Engineering
    The Software Delivery Notebook
    The changing state of Platform Engineering
    Loading
    /

    Drawing on the findings of the most recent two volumes of the State of Platform Engineering report, this episodes looks at the difference between shift-left and shift-down, portal traps, and abstract requirement satisfaction. There’s also a look at AI in platforms and platforms for AI.

    There’s also this idea of platform pluralism. We used to chase the mythical single platform to rule them all, the data says that’s the wrong goal.

    You’ll also hear about the measurement crisis, which has been validated in multiple reports from different research teams.

  • State of AI vs Human Code Generation

    State of AI vs. Human Code Generation
    The Software Delivery Notebook
    State of AI vs Human Code Generation
    Loading
    /

    CodeRabbit looked at 470 open-source pull requests and produced the State of AI vs Human Code Generation report with their findings.

    Crucially, AI makes 1.7x more errors, increasing major and critical defects. The AI-authored/assisted changes cause problems with logic errors, security vulnerabilities, and performance regressions (whereas humans are more likely to make spelling mistakes or have testability issues).

    That means the AI is introducing foundational risk that a competent developer should be catching very early. Is the training data just poisoning the model with old insecure patterns?

  • Engineering performance and AI impact 2025 Report

    Engineering Performance and AI Impact 2025 Report
    The Software Delivery Notebook
    Engineering performance and AI impact 2025 Report
    Loading
    /

    This week we look at the LeadDev and Honeycomb Engineering Performance report 2025, which is based on 400+ survey responses from engineering leaders.

    Find out what they’re measuring performance and how they work out whether AI is having an impact.

  • The hard truth about Platform Engineering

    The hard truth about platform engineering
    The Software Delivery Notebook
    The hard truth about Platform Engineering
    Loading
    /

    Based on the 2025 Platform Engineering Pulse report from Octopus, we look at what’s happening in practice.

    Within the Platform Engineering (PE) community we talk about reducing developer burnout, taking a product not project approach to platforms, and making platforms optional. The reality is that organizations care more about standardization and efficiency and they want to force developers to use what gets built.

    This creates a disconnect between the views on success, with those making platforms thinking everything is great while developers don’t see the goals being met.

    So the DevEx benefit is real, but it might be a happy side effect rather than the main reason the check got signed.

  • DORA’s State of AI-Assisted Software Development report

    DORA 2025: State of AI-Assisted Software Development
    The Software Delivery Notebook
    DORA’s State of AI-Assisted Software Development report
    Loading
    /

    DORA has published their latest report and it goes deep into AI-Assisted Software development. It covers the extent of adoption, how it moves the needle on outcomes, and (crucially) what you need in place if you want to succeed.

    As well as thoughtful and thorough analysis on software delivery with AI assistance, the report also looks at different team types and how throughput and stability happen together, not in conflict with each other.

    Burnout, friction, and instability are on the list of things to watch out for, so find out how you can avoid amplifying the bad stuff, and boost the positive outcomes instead.

  • Achieving Continuous Delivery with TPF

    Achieving Continuous Delivery with TPF
    The Software Delivery Notebook
    Achieving Continuous Delivery with TPF
    Loading
    /

    This episodes look at the white paper Achieving Continuous Delivery With TPF by Bob Walker at Octopus Deploy. TPF is a set of three practices that can solve many CI/CD pipeline problems.

    • Trunk-based development
    • Progressive rollouts
    • Feature toggles

    Find out the core problems and how TPF helps, with some case studies that might hit close to home.

    TPF is much simpler, much more elegant. With trunk-based development those small frequent merges mean the main branch is basically always deployable, it’s always green.

    And then feature toggles hide any work in progress, so a new feature that’s half done doesn’t block a critical bug fix or performance improvement.

    Progressive rollouts let you get the new version deployed and fully verified in production.

  • Westrum’s study of information flow

    Westrum's study of information flow
    The Software Delivery Notebook
    Westrum’s study of information flow
    Loading
    /

    Ron Westrum is famous for his classification of organizational culture, but he’s also done great work on hidden events, and information flow. This episode looks at Westrum’s study of information flow and it contains highly relevant lessons for all organizations, not just safety-critical industries.

    When information fails to flow, it stops the “safe and proper functioning of the organization,” and looking at the flow of information is a powerful indicator of how well the organization functions.

    The properties of great information are receiver-centric. Good information…

    1. Answers the questions the receiver needs answered
    2. Is timely
    3. Is presented in a way that makes it usable by the receiver

    This paper has a whole host of insights, explored through interesting real-world stories.

  • Unpacking Weinberg’s laws of consulting

    The Principles and Practices of Consulting
    The Software Delivery Notebook
    Unpacking Weinberg’s laws of consulting
    Loading
    /

    Based on a list of laws, rules, and principles that span Gerald M. Weinberg’s two books on The Secrets of Consulting. These laws are a helpful and amusing way to get into the consultant mindset.

    They include The First Law of Consulting:

    In spite of what your client may tell you, there’s always a
    problem.

    And The Second Law of Consulting:

    No matter how it looks at first, it’s always a people problem.

    Enjoy the truth and fun of this collection of insteresting thinking angles.

  • Compliance through Continuous Delivery

    Continuous Delivery through CD
    The Software Delivery Notebook
    Compliance through Continuous Delivery
    Loading
    /

    Based on the financial industry survey by Octopus and their Compliance through Continuous Delivery report, this episode shows how recent regulations are increasing the pressure for regulated companies to improve their software delivery performance.

    You can’t meet the requirements without having a path to production that applies to all changes, whether they are routine features or security patches.

    Find out why you need to ditch the expedite process, kick out the cross-departmental approval committees, and embrace Continuous Delivery to improve your compliance.

    It becomes very clear that organizations without automated deployment pipelines really struggle. They just can’t meet the demand for increased deployment frequency that this kind of legislation requires.

    It sounds like Continuous Delivery and DevOps aren’t just nice to haves any more, they’re becoming essential for survival, especially in regulated industries.

  • Why software projects fail

    Why Big Software Projects Fail
    The Software Delivery Notebook
    Why software projects fail
    Loading
    /

    Let’s look at a classic software projects paper published in The Journal of Defense Software Engineering in March 2005. It discusses why software projects fail so often. Some of the concepts discussed are old school and the criteria for success aren’t what we’d use today, but it’s a fascinating snapshot of the problems that were faced in the old times.

    Despite its age, we still find some of these problems can surface in modern software delivery. Understanding where we came from can help guide what we do next.

    Watts S. Humphrey asks 12 questions in his paper:

    1. Are all large software projects unmanageable?
    2. Why are large software projects hard to manage?
    3. Why is autocratic management ineffective for software?
    4. Why is management visibility a problem for software?
    5. Why can’t management just ask the developers?
    6. Why do planned projects fail?
    7. Why not just insist on detailed plans?
    8. Why not tell the developers to plan their work?
    9. How can we get developers to make good plans?
    10. How can management trust developers to make plans?
    11. What are the risks of changing?
    12. What has been the experience so far?