Quick, light read. A humane take on programming management. The division of roles in the software development process feels a antiquated, but leaves me distressed about the extent to which most teams forget to perform some of the tasks. (Generally figuring out what "the customer" wants without becoming bogged down in programming details.)
Plenty of mentions of computing time, tapes, etc that are (fortunately) archaic, but everything else remains relevant, and unlearned by modern management.