21. Understanding a Story

    💡 We interview the customer or domain expert to uncover the entirety of the essential complexity for a feature. With pseudocode, we turn our vague understanding into a detailed one that can be broken into smaller parts, understood by the customer, and eventually acceptance tested.

    It's true. Every customer is out there to make your life a little bit more miserable by tossing in additional requirements just as you thought…

    Let's resend your copy of the 📕
    Enter your email that you used to purchase it with.

    Howdy 👋

    This is an online wiki about the main topics over the last 40 years of software design, architecture & testing. It was created by Khalil Stemmler.

    This wiki's mission is to help eliminate the unknown unknowns, helping you get up to speed on the best practices and principles to write testable, flexible, and maintainable code.

    I created this wiki while I was connecting the dots on my own path. You can read more about that learning journey in the introduction

    Already bought it?

    If you’ve already purchased the book, click here to re-send your link. You can read the online wiki or download a copy of the book in PDF, EPUB, and Kindle versions.

    Want access?

    You can read the intro to the book for free and visit solidbook.io to buy the book/wiki! To get an idea of my writing, read some of my best free content here and here.

    Need help?

    Something not working? Have a question? You can reach me on at khalil@khalilstemmler.com.