I recently read through that book and it's nuts both how prescient it is and how different some of the suggestions are than what anyone now would consider.
For instance, there was talk of a team structure with one programmer and everyone else in specialized, supporting roles. That wouldn't fly today because everyone is obsessed with employee fungibility and bus factor.
> That wouldn't fly today because everyone is obsessed with employee fungibility and bus factor.
Rightly so. Job hopping is much easier in the software industry now than it was when that book was written. Average tenure in software jobs is significantly lower than the average for all professions, and even that general average is only around 4 years.
For instance, there was talk of a team structure with one programmer and everyone else in specialized, supporting roles. That wouldn't fly today because everyone is obsessed with employee fungibility and bus factor.