Factually not true. I suggest you grab a copy of "In Search of Stupidity by Merrill Chapman":

https://www.amazon.co.uk/Search-Stupidity-Twenty-Marketing-D...

Most of these companies from the 80's and 90's foot gunned themselves into oblivion or were bought by companies that ruined their products.

It's about even more than that: it's about the complexity.

There's an inherent complexity in the problem being solved.

And there is an "accidental complexity" in the implementation of the solution.

Throwing away everything, people typically believe that they can avoid handling a lot of the "inherent complexity." But typically there is a good reason why the inherent complexity was addressed in the previous version of the program, and there's a big chance that the new "from the scratch" designers will have to relearn and rediscover all that, instead of transforming the already existing knowledge that is encoded in the previous version.

For anybody interested in the topic, I recommend the number of case studies presented in:

https://www.amazon.com/Search-Stupidity-Twenty-Marketing-Dis...

"In Search of Stupidity: Over Twenty Years of High Tech Marketing Disasters"

See about new rewrite of Wordstar simply not having the printer drivers that the previous had, and also other features people already expected, leading to Wordstar's demise.

Or what Zawinski's names "Cascade of Attention-Deficit Teenagers" (search the internet for that, the link here wouldn't work!)

"I'm so totally impressed at this Way New Development Paradigm. Let's call it the "Cascade of Attention-Deficit Teenagers" model, or "CADT" for short."

"It hardly seems worth even having a bug system if the frequency of from-scratch rewrites always outstrips the pace of bug fixing. Why not be honest and resign yourself to the fact that version 0.8 is followed by version 0.8, which is then followed by version 0.8?"

Or an interview with Jamie Zawinski from Siebel's "Coders at Work."

https://www.amazon.com/Coders-Work-Reflections-Craft-Program...

... "even phrasing it that way makes it sounds like there’s someone who’s actually in charge making that decision, which isn’t true at all. All of this stuff just sort of happens. And one of the things that happens is everything get rewritten all the time and nothing’s ever finished. If you’re one of those developers, that’s fine because there’s always something to play around with if your hobby is messing around with your computer rather than it being a means to an end — being a tool you use to get whatever you’re actually interested in done."

If one is able to cover all the complexity, and it is not destructive to the goal, the rewrite is OK. Otherwise, one should be critical to the ideas of rewrites as they could be potentially secretly motivated by simple (jwz again): "rewriting everything from scratch is fun (because "this time it will be done right", ha ha)"

If you're interested in older Silicon Valley history,

In Search of Stupidity: Over Twenty Years of High Tech Marketing Disasters ( https://amzn.to/2EJjvHG )

is pretty good, although he gets some things pretty wrong himself, like the rise of open source.

Any more anecdotes? "In Search of Stupidity" by Rick Chapman covers stupidity before digital nomads (https://www.amazon.com/Search-Stupidity-Twenty-Marketing-Dis...).

But, it sounds like digital nomadry is a tool being misused like other tools in this Dilbert-esque environment you work in. How do I get a job in this marketing dept.? I have NO experience in marketing, but my common sense is good half the time. I'm sure I can make fewer blunders than the current team.

This is a very nice compilation: https://www.amazon.com/Search-Stupidity-Twenty-Marketing-Dis...

One of my favorites this year, particularly in non-fiction, is In Search of Stupidity by Merril R. Chapman [0]. It's an amazing look at the history of microcomputers and the ensuing software market with a particular eye on what made certain companies fail.

Chapman worked for sometime in sales and later product management at MicroPro (WordStar), Ashton-Tate, Novell, etc... so it has quite an "inside-look" feel and the subject matter sounds like it's treated fairly.

The narrative is quite the page-turner for a non-fiction book, but my only qualm with it is that Chapman can be pretty sophomoric and unnecessarily gratuitous in his lampooning and shaming of business leaders or strategies which flirts with undermining the otherwise really insightful analysis.

It's a little dated (Microsoft is still king and Apple the scrappy underdog), but I think it's an important context for anyone following tech today.

[0] https://www.amazon.com/Search-Stupidity-Twenty-Marketing-Dis...

In Search of Stupidity: Over Twenty Years of High Tech Marketing Disasters

http://www.amazon.com/In-Search-Stupidity-Marketing-Disaster...

"Casting The Net" is a good companion book to "Where Wizards Stay Up Late" already mentioned here:

http://www.amazon.co.uk/dp/0201876744

Again, and already mentioned, "The Soul of a New Machine" by Tracy Kidder is a great read. It's a particular favourite what with being an ex-Data General field engineer (maintained and fixed Nova 3/4 and Eclipse S/130/140's and associated peripherals).

I can also recommend "In Search of Stupidity:Over 20 Years of High-Tech Marketing Disasters" which about how the old giants of the early PC software industry (Ashton Tate, MicroPro et al) made colossal mistakes resulting in their extinction.

http://www.amazon.co.uk/dp/1590597214

This reads a bit like something from

http://www.amazon.com/In-Search-Stupidity-Marketing-Disaster...

albeit with more focus on the features and less on what led Quark to screw up.