Books on Writing betterLiterature about better writing
Which are the best books on writing proper codes?
Whilst I concur with most responses that books are not (on their own) the best way to writing proper writing, they are a great addition to other things you could do (like read codes, have your codes checked, etc.). It' Uncle Bob's neat code: This is a very individual opinion about why it is important to create good codes and what makes good them.
Clearly documenting the traps that poor coding can cause and not crushing words ("[bad coding will force an organisation to its knees" and "programmers who are content with just working coding behave unprofessionally"). The most important thing is that it will help you equip your brain for what I think is the most important part of writing good code: empiricism (for others who will be reading your source and even your self-to-may.).
The" Pathfinder rule", for example, is a good way to work ("leave things in a better state than they were found"). But on the other hand, it's a little less "structured" than Code Complete, but that didn't disturb me. Code-Complete: I received a copy of it on my first working days at Google.
It is the definite guideline for writing codes. So, I would definitely begin with clean codes. Once I was described that the Bible is a Code Complete, and Clean Cod is the manual. One last note: Many folks will point out that most of the contents in these books are evident and intuitively, but at the end of the days the issue is often not known, it is not remember.
It is not a target in itself to create clear codes. All you really want to do is writing serviceable codes. It is important: If, for example, you say that you should use small method, the dot is not there. Small them if the resulting source is easier to manage (mostly), but otherwise make them large.
Complet is the best work I' ve ever seen to teach me how to spell serviceable codes. In contrast to the Clean Coding many suggestions are not made on the basis of the author's own taste, but on the basis of rigorous research. It is independent of languages and covers all facets of writing codes.
Apart from that: The Bragmatic-Programmer is a great way to learn the maintenance friendly cod. It is a beautiful first volume on this topic. When you don't have an account with Complete, it' another good reading for you. After all, Clean Coding is still a good work. I' d definitely suggest Clean Code:
Standardisation is the buzzword to legible codes. Uncompliant codes create disarray. You' ll need additional work to find out why there was a modification of the "rules" for a particular item of script. Styloguide for Angular 1. x apps. https://github. com/johnpapa/angu..... Cory in this video will recommend reading an algorithms aloud to see if it is reading well.
It accentuates the similarities between encoding and writing (literature). It is probably because it is "dirty" if it does not read your TC. When you are writing in a foreign tongues, I suggest you take a look at Give Clean Codes the Importance it Deserves, where our CTO deals with this area!
Writing proper coding is best done with Styleguides, Codeviews and example codes. Here you can find Styleguides from Google and Open source products like Firefox and Linux. There is a great deal of institutionality in good stylistic guidelines, and you can take up many good customs by following one of them.
Reading other people's codes is the best way to get to know how to create proper codes. You' ll be learning very quickly, making reading codes tough. My personal preference is to choose languages rather than introduction books / guides / workouts. You can find the Cleans and books credentials in the site's public wiki: http://wiki.clean.cs.ru.nl/Docum...