In this case it's possible to recognise both that Taligent inadvertently subsidised production of a nicely packaged collection of "best practices" (taken individually, the TOC topics lgtm) and that shipping crap dominates designing (maybe even building?) according to best practices but never invoicing.
(I don't know if it's still true, but for a long time last century the "secret sauce" of Silicon Valley was that it was easy to find people who had just come off of one of these grand "new new thing" Потёмкин projects, and both (a) wanted to ship this time around, and (b) knew the best corners to cut to do so)
Technology developed by Taligent landed in other projects, for instance, the Java JDK.
> in early 1996, IBM had assumed full ownership of Taligent, the joint venture started by IBM and Apple and later joined by HP. Taligent had been developing an object-oriented application framework and operating system called CommonPoint, which included extensive international support. When IBM took over, CommonPoint was mothballed, but much of the underlying technology was integrated into other IBM products.
Fairly quickly, the management of IBM and Taligent came to a realization: Java was missing international support. But Taligent had great international technology, talented engineers--including Dr. Mark Davis, president of the Unicode Consortium--and a location about 100 meters from Sun's JavaSoft division in Cupertino, California. Thus, a partnership was born: IBM arranged for Taligent's Text and International group to contribute international classes to Sun's Java Development Kit, making Java powerful enough for real-world business applications.
For JDK 1.1, Taligent provided the new java.text package, plus a number of new classes in java.util. This included Format and all its subclasses for formatting dates, times, numbers and messages; Collator, for language-sensitive string sorting; and BreakIterator , for determining line, word, and sentence boundaries in Unicode text. In java.util, Taligent contributed parts of ResourceBundle, as well as the Calendar and TimeZone classes (which provide flexible, international-friendly date and time support). In addition, IBM contributed a large collection of locale data from their National Language Technical Center in Toronto. This API and data provide a standard way to handle the requirements of different countries and languages, making this transparent to developers.
https://icu-project.org/docs/papers/history_of_java_internat...
I seem to recall a rumour that these were not given to experienced engineers to implement.
"Those who can do, do. Those who can't, teach."
It implies that teaching isn't a skill of its own. Some of the best football coaches were mediocre players (Alex Ferguson, Jose Mourinho) and some of the best players turned out to be very poor coaches (Steven Gerrard springs to mind at the moment). Can you only learn physics from someone who has made a world-changing discovery, or learn to write from a best-selling author? Or do you learn from someone who knows just enough to guide you in the right direction with enthusiasm and correct your mistakes in a way that doesn't make you feel like a failure?
What is correct is dogma in software development is a problem - software is too malleable and the world changes too fast to allow one set of ideas to dominate everything. That lesson hadn't even been thought about in the 90s though.
Expensive consulting services, training courses, books, videos, etc. It's not about whether any of that stuff actually works; it's about essentially creating a religion and extracting profit from the gullible.