There are are many great ideas in TDD, Lean, and in how Lean has been attempted to be applied to software development. Many of those ideas are worth keeping. Some ideas need to be expanded to apply to more of the process. Some ideas need to change. And some need dropped, or at least, de-emphasized.
We will do just that, examine the principles of TDD and Lean, examine the "why" of those principles, mix in some other ideas, and then derive some practical practices that make sense to practice in the building of current software projects.
epub works great on Kindle, for example
You get both pdf and epub, and will be notified of updates as they come out.
Introduction - 2nd draft
Essential Components - 1st draft
Building on TDD - 1st draft
Building on Lean - 1st draft
Finding Waste in TDD
Pragmatism
Lean TDD
Staying Lean
What about ...
Considerations
Conclusion
pdf version
epub version (for eBook readers like kindle)
all updates up through and including the final production ready version
There are a couple of ways.
The easiest is to log in and drop the epub file at amazon.com/sendtokindle
You can also set up email so that you can just email the epub file to your device. See amazon.com/gp/sendtokindle/email/
All other e-readers should accept epub format.
You also get the pdf version.
You're essentially purchasing an in-progress book. I've been meaning to write this book for at least 4 years, and have decided that writing it in public, with invested readers, is the best way to motivate me to finish it in a timely manner
You'll be reading essentially the first typed version, the first draft. There may be errors, typos, ommissions, etc. I'd love help in finding those issues. I'd also appreciate questions and commentary around topics you think would be good to include in the book. The book includes information on how to submit a problem, but it's not a secret, I've set up a repo to collect issues here.
The purchase process includes entering an email address. I'll use that email to notify you of updates to the book, either new chapters, or edited chapters.
I'm calling it an "alpha version" as I'm writing the first draft. Some chapters may take a week to finish. Some chapters may take 2 weeks, but I'll try to release wherever I'm at on a weekly basis. I'd really like to be done with the first draft (alpha version) by the end of the year.
After the "alpha", I'll take the feedback gathered so far and work through updates. That phase will be "beta".
Actually, it's possible I may flip the designation from "alpha" to "beta" once the first draft is, say, 70-80% done. We'll see how it goes.
Once the beta is complete, I'll make one more pass through (at least). This time, I'll be recording an audio version for an audio book format, and reading it aloud may point out awkward sentences that need fixed.
When all that is done, I'll call it production ready, and probably release it on more platforms.
Purchasing this in-progress book will get you all updates, including the edition I consider the "production ready" version.
The audio book will be a separate purchase, and I'm not sure what platforms it will be available on. I honestly haven't thought that far yet.