Clean Code – Notes
smalldata.tech
Clean Code – Notes
1–6 of 6 posts
Re: Clean Code – Notes
#2I must admit I was expecting a bit more based on the article's title
Re: Clean Code – Notes
#3I think that Notes and Cheatsheets are a pretty good in general, but they don't replace the book contents itself. In my opinion the process of reading is important to understand...
I also noticed, that a lot people talking about the principles of "Clean Code" (either PRO or CON) did NOT even read the book (entirely) nor hat other sources of wisdom ;)
Re: Clean Code – Notes
#4I think that Notes and Cheatsheets are a pretty good in general, but they don't replace the book contents itself. In my opinion the process of reading is important to understand... I also noticed, that a lot people talking about the principles of "Clean Code" (either PRO or CON) did NOT even read the book (entirely) nor hat other sources of wisdom ;)
Does one need to eat the whole pie to tell how the pie tastes? What if we are talking about baking an apple pie ;)?
Re: Clean Code – Notes
#5I think that Notes and Cheatsheets are a pretty good in general, but they don't replace the book contents itself. In my opinion the process of reading is important to understand... I also noticed, that a lot people talking about the principles of "Clean Code" (either PRO or CON) did NOT even read the book (entirely) nor hat other sources of wisdom ;)
Although I agree, coding practices should be added incrementally so that they have time to become habits. Nobody can remember hundreds of rules while working on a code base.
This kind of notes are useful I think.
Re: Clean Code – Notes
#6I think that Notes and Cheatsheets are a pretty good in general, but they don't replace the book contents itself. In my opinion the process of reading is important to understand... I also noticed, that a lot people talking about the principles of "Clean Code" (either PRO or CON) did NOT even read the book (entirely) nor hat other sources of wisdom ;)
> I also noticed, that a lot people talking about the principles of "Clean Code" (either PRO or CON) did NOT even read the book (entirely) nor hat other sources of wisdom ;)
In your opinion, why do you feel any of those points you made are relevant or have any substance? I mean, the importance of Clean Code is to improve your output by following a few guidelines, not be pedantic and use the book as bible to bash others in bike shedding discussions.