Wonderful book. There's a snippet on conflicts between engineers and how engineers approach them - often not in the best way - that I've referenced so many times in my career.
Great book. I relentlessly and boringly quote the commandment from the CEO in that book that there was to be "no mode switch".
I have found this to be a great rule of thumb in software too. Engineers often first instinct is to add "advanced mode", "legacy mode" or whatever. Often with no idea how much trouble having two modes of behaviour will cause downstream in training, understanding, compatibility etc.
