Wartime Software: Building Software when Speed Matters

by David B. Black

This is a book about building software when competition is fierce and speed and accuracy matter.Most people assume there is one “right” way to build software, and that’s that. While there are various fashion trends that infect software from time to time, none of them are as different as they like to think they are. There are some important but little-discussed facts about the mainstream consensus of software •It is mostly organized to give non-technical people confidence that things are OK, meaning on-time and on-budget. Its highest principle is predictability. Not speed.•It mostly doesn’t work. Studies support what everyone in the field most projects fail outright, or have their goals changed to avoid admitting failure.So what we have are methods that are slow – and produce crappy results! What happened to slow but sure, or slow but steady? What we’ve got is slow and stupid.If everyone you compete against uses the same crappy methods, you’ll be OK. Your projects will be perpetually late and disappointing, but so will everyone else’s, so you’ll be performing “up to standard.”But what if you’re not? What if you’re competing against a group that gets way more done in much less time? I’m not talking 10 or 20% here; I’m talking many whole-number factors, like 10, 50 or more. What’s going to happen? It’s you’re going to lose! If that’s OK with you, don't read this book. You’ll be happier. This book is part of a series devoted to Building Better Software Better, i.e., achieving superior results (better software) through optimal methods (building software better).

74 pages, Kindle Edition

First published May 16, 2013

Reviews

[Fetcher · Rating 1 out of 5]

DNF - I am not a software developer, but was asked to read this book as part of a leadership meeting. While it is not a long book, I made it two thirds of the way through before giving up. From what I read, this advice goes against every large company software development process and assumes additional risk.

[Liam Hazell · Rating 4 out of 5]

Not the most modern in terms of specific technical advice, but I think a lot of the over arching themes are even more important today. Great read.

[Janno Teelem · Rating 5 out of 5]

David has been a developer since 1968. He explains why the popular software development practices often fail and what actually needs to be done if your goal is to deliver working software quickly. Highly recommended, especially for people working in startups.