This is clearly visible in the HR requirements practices. Companies which have a confidence in their ability to manage the on-boarders' attention, tend to interview for communication rather than experience - those who haven't made the investment in attention-management techniques, such as great training, technical on-boarding routine, etc., tend to focus on experience over sociability.
>Brookes' law
I've found, with 30 years of experience in software development from both the trenches to management and back, that there is an aspect of this law which goes ignored - "Adding manpower to a late software project makes it later, but adding documentation to a late software project makes it easier to add manpower.."
The better you document things so that strangers can understand them, the easier time you have on boarding strangers and getting them up to speed. This is a cultural mechanic, and alas is usually in the wrong persons' hands - i.e. HR, upper managements, etc. Technical people need to get this right for the true fire to burn ..
I think this is shared by all big engineering works.
> This is a cultural mechanic
I'd call this "structural" instead of "cultural", where I am of the opinion that culture is implicit and structure is explicit in nature.
I wonder how we came to such abject differences?
This stayed with me. I think I recently read a similar statement again in some text.
> Software is not labor-intensive. Not many people are necessary in order to produce good software.
Not many people are needed to produce 500gr of good rice. And lots of people are needed to produce something like all the software Google or MS maintains.
The specialty of software is the low cost of marginal products. This is the new thing here, not labour intensiveness.
> On the contrary, Brooks’s law on software project management states that “adding manpower to a late software project makes it later”.
This has more to do with communication, collaboration and slowness of getting up to speed when joining a software project.