Status Updates From The Clean Coder: A Code of ...

More practical advice followed. Quite some time spent on testing side of things. It seems to be fairly universal, ie do more unit tests followed by component, integration, functional, acceptance, qa. I liked the suggestions on how not to cow under pressure and be open if something is not possible, ie do not say you will try things. Estimation suggestions and the formula given is also quite useful.

2 chapters in and all I can say the authos in the spot. It is difficult for the engineers to learn to be professional when you have the divide and conquer tactics in the tech companies. If all you did in your life was to work with a manager and never saw how other engineers fight for proper implementation then that person will just repeat the mistakes. This book will help you understand. Content maps to my experience