Brooks's insight that adding programmers to a late project makes it later - now known as Brooks's Law - remains one of the most cited observations in software engineering more than four decades after publication. Eric Evans, Kent Beck, and Martin Fowler all reference his distinction between essential and accidental complexity as the intellectual foundation for their own approaches to domain modelling, test-driven development, and enterprise architecture patterns.
The book's influence extends into engineering management, with Camille Fournier connecting Brooks's observations about communication overhead to the challenges of scaling modern tech organisations. Some readers note that specific technical examples feel dated, but the core principles about complexity, communication, and the human limits of coordination are considered timeless - the Google SRE book still cites it when discussing team scaling.