3 ms·

The MMM was first published in 1975. I began working in the industry in 1978 and first read his book around then. Thirty-eight years later, we still try to fix

The MMM was first published in 1975. I began working in the industry in 1978 and first read his book around then. Thirty-eight years later, we still try to fix late programs by adding people. Brooks wrote the seminal, magnificent book on project management but he's still a voice, crying in the wilderness.

vram22 11y ago
>Thirty-eight years later, we still try to fix late programs by adding people. How true. >Brooks wrote the seminal, magnificent book on project management but he's still a voice, crying in the wilderness. But he's not the only voice any more. I'm sure there are some others, but one I know of is Rich Hickey. Okay, not for the exact same topic as Brooks, but a closely related one, IMO. Coincidentally, I had blogged about a video of him talking at a Clojure meet just yesterday (after watching it for the second time in some months, because I found it good). The topic is not Clojure, it's what he calls (jokingly) Hammock-Driven Development; IOW, thinking about, and analyzing enough, and deeply enough, your work [1], up front, because that is the better way and actually saves costs over the project lifetime (proven by studies, such as Capers Jones [2] et al). Here's the blog post, with a link to the video: http://jugad2.blogspot.in/2016/03/tech-video-rich-hickey-hammock-driven.html http://jugad2.blogspot.in/2016/03/tech-video-rich-hickey-ham... or you can watch the video directly here: [1] And what he recommends is not the waterfall model or UML, BTW. In fact, he explicitly mentions and does not recommend them. But goes on to say, don't throw the baby out with the bathwater. See the video to get the rest. [2]: https://en.wikipedia.org/wiki/Capers_Jones https://en.wikipedia.org/wiki/Capers_Jones http://namcookanalytics.com/about/ http://namcookanalytics.com/about/ Edit: I like this Capers Jones quote: "High-quality software is not expensive. High-quality software is faster and cheaper to build and maintain than low-quality software, from initial development all the way through total cost of ownership."[4]

vram22 11y ago

>Thirty-eight years later, we still try to fix late programs by adding people. How true. >Brooks wrote the seminal, magnificent book on project management but he's still a voice, crying in the wilderness. But he's not the only voice any more. I'm sure there are some others, but one I know of is Rich Hickey. Okay, not for the exact same topic as Brooks, but a closely related one, IMO. Coincidentally, I had blogged about a video of him talking at a Clojure meet just yesterday (after watching it for the second time in some months, because I found it good). The topic is not Clojure, it's what he calls (jokingly) Hammock-Driven Development; IOW, thinking about, and analyzing enough, and deeply enough, your work [1], up front, because that is the better way and actually saves costs over the project lifetime (proven by studies, such as Capers Jones [2] et al). Here's the blog post, with a link to the video: http://jugad2.blogspot.in/2016/03/tech-video-rich-hickey-hammock-driven.html http://jugad2.blogspot.in/2016/03/tech-video-rich-hickey-ham... or you can watch the video directly here: [1] And what he recommends is not the waterfall model or UML, BTW. In fact, he explicitly mentions and does not recommend them. But goes on to say, don't throw the baby out with the bathwater. See the video to get the rest. [2]: https://en.wikipedia.org/wiki/Capers_Jones https://en.wikipedia.org/wiki/Capers_Jones http://namcookanalytics.com/about/ http://namcookanalytics.com/about/ Edit: I like this Capers Jones quote: "High-quality software is not expensive. High-quality software is faster and cheaper to build and maintain than low-quality software, from initial development all the way through total cost of ownership."[4]