When I began programming it was a book I respected. I read it twice. But today it is a book I see with flaws. I think it is a dated book, made for an era chang

When I began programming it was a book I respected. I read it twice. But today it is a book I see with flaws. I think it is a dated book, made for an era changed by web development, agile and functional languages. My criticisms: * It worries too much about little details on verbose object oriented languages (Java, C++). It is overly obsessed about ahead planning. * it established myths that I am not sure to be true (cone of uncertainty, orders of magnitude different productivity among programmers). * it failed to understand the agile philosophy and why it's ideas generate more adaptable software I think Pragmatic Programmer is a more interesting book.