Now this is a chapter that sounds intriguing actually they all strike a note (
TOC).
I have read many books on different programing language, frameworks etc. etc. but never one on writing code. What is in this book that other books concentrating on grammar and design do not show to the reader? Is it going to teach me how to make good trade offs? In situations when "The best laid plans" are impossible in the face of reality (read requirements/wishes) and the "The need for speed" is ever so present on your shoulder will I get a "Recipe for a program" that will aid with those "Grand designs" "Testing times". Sorry for the poetic excursion, I guess what I am asking is what does the book "preach" about coding and are there good stories in it to keep me reading??
I have always tried to stuff my head with different practices, ideas and directions people a lot more experienced, but I am finding that I have my own way of writing code and that I come up with solutions distinctive in their own right. Will the book expose any situations with real world example and provide the authors best advice? Can you share an example?
Thank you in advance.