Post by rubina9898 on Dec 24, 2023 3:30:59 GMT -5
A supporter of the approach that good code comments itself personally I think this statement is harmful . On the contrary the author presents guidelines on how to write good comments what they should contain and when they should be written . In addition to this book you can learn more about this topic in my article Comments in Code . Nevertheless I think that in the chapter describing the comment first approach the author "flowed" a bit. I often write in a comment a list of steps that my code should perform in the form of pseudocode. However after writing the implementation I remove the previously prepared pseudocode. I consider documenting code before writing it to be style over substance and more of a problem than a potential benefit.
The code is a living creation which is evident from the content of the book under review. The code is changed frequently so the documentation also needs to be modified. There have been Phone Number List many times when I have written code only to delete it a moment later and start implementing it again or testing a different approach. In addition to comments the author also pays attention to the readability and consistency of the code . A separate chapter is devoted to the issue of appropriate naming in the code. This often saves some of the comments already mentioned. There always has to be a but While the vast majority of the book provides a lot of valuable knowledge the Software Trends chapter is in my opinion forced.
The author covers many classic issues related to software development such as unit tests TDD design patterns and the object oriented programming paradigm . Nevertheless all these topics are treated very superficially and the quality of the chapter in question lags behind the rest of the book. The chapter itself also doesn't add much to the rest of the book. The book would lose nothing if this chapter were cut out. It may have added value for very early stage developers but I don't think they are the target audience for the rest of the book.
The code is a living creation which is evident from the content of the book under review. The code is changed frequently so the documentation also needs to be modified. There have been Phone Number List many times when I have written code only to delete it a moment later and start implementing it again or testing a different approach. In addition to comments the author also pays attention to the readability and consistency of the code . A separate chapter is devoted to the issue of appropriate naming in the code. This often saves some of the comments already mentioned. There always has to be a but While the vast majority of the book provides a lot of valuable knowledge the Software Trends chapter is in my opinion forced.
The author covers many classic issues related to software development such as unit tests TDD design patterns and the object oriented programming paradigm . Nevertheless all these topics are treated very superficially and the quality of the chapter in question lags behind the rest of the book. The chapter itself also doesn't add much to the rest of the book. The book would lose nothing if this chapter were cut out. It may have added value for very early stage developers but I don't think they are the target audience for the rest of the book.