Ask Fakespot Chat questions about this productAlpha
Add detailed feedback
Message
Loading suggested questions
Suggested Questions
Suggested Questions
No suggested questions were found
Highlights
Quality
We programmers are optimists and enjoying our craft is what essentially allows us to get by in the product development lifecycle
In my snarkier moments i like to think that a lot of systems engineering at least at the beginning was just software engineerin... Read More
I agree with the author on no silver bullet
He believes the critical need to be the preservation of the conceptual integrity of the overall product
Price
The stable price reflects this classic wisdom
Finally a programming system component costs 9x as much
Competitiveness
Unfortunately building a small sharp team shouldnt by consensus exceed 10 people
This book seems pretty old but has million 5stars scores
Overview
- How are reviewers describing this item?
still, many, first, most and great. - Our engine has profiled the reviewer patterns and has determined that there is minimal deception involved.
- Our engine has determined that the review content quality is high and informative.
- Our engine has detected that Amazon has altered, modified or removed reviews from this listing. We approximate total reviews altered up to 24.
- Our engine has discovered that over 90% high quality reviews are present.
- This product had a total of 558 reviews as of our last analysis date on Dec 20 2020.
Helpful InsightsBETA
Posted by a reviewer on Amazon
Some project examples from the past are still valid today in 2016 and in that way the book is still relevant to any software engineer or producer
Posted by a reviewer on Amazon
It is not so much that its solutions to software design problems are still relevant — they are frequently decades out of date
Posted by a reviewer on Amazon
Rather it is a classic for its description of enduring software design problems
Posted by a reviewer on Amazon
Fred brooks was a software engineer at ibm for some decades and later chair of the unc cs department
Posted by a reviewer on Amazon
The 18th chapter is a summary of all prior chapters while the 19th chapter reflects on the book 20 years later in 1995 what changed and what hadnt
Posted by a reviewer on Amazon
The book is a little bit old for a software engineering guide
Posted by a reviewer on Amazon
However it speaks about problems that we still face today
Posted by a reviewer on Amazon
A great book that tells you everything your project manager and lead architect are doing wrong leading to the depressing realization that there is nothing you can do
Review Count History
Price History
Ask Fakespot Chat questions about this productAlpha
Add detailed feedback
Message
Loading suggested questions
Suggested Questions
Suggested Questions
No suggested questions were found