Comment by babybjornborg

I read this book last year and this application is spot on. There is a point in the narrative when the company automates a step in their manufacturing using an expensive machine and it has the effect developed here: the next step in the process is backed up further.

The points specific to software where it might not even be producing in-spec is also very good.

Comments that cite the solo dev/prototype case are of course not what this is getting at, but it's one good use of quick generation.

I would extend this article by saying what The Goal says, namely that the goal of every firm is to make money, and everything is intermediate to that. So whether or not software architecture is grade-A or grade-C, it's only ever in this subservient role to the firm's goal.