{"product":{"product_id":"0132350882","title":"Clean Code: A Handbook of Agile Software Craftsmanship","price":"40.0","image_url":"https://m.media-amazon.com/images/I/41xShlnTZTL._SL500_.jpg","url":"https://www.amazon.com/dp/0132350882"},"comments":[{"body":"I always recommend [this book called 'Clean Code'](https://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882)  \r\nIt details a collection of techniques to keep your code readable and maintainable.  \r\nIn general use good variable and method names and use more, shorter methods where appropriate","subreddit_name":"learnprogramming","author":"batmassagetotheface"},{"body":"\u0026gt;What are your favorite resources out there that you turn to, that could be helpful in showing someone what a good review is?\r\n\r\n[Clean Code by Robert C. Martin](https://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882).  \r\n\r\nThis book covers all kinds of great stuff regarding correctness, maintainability, testability, etc. \r\n\r\nI want to call your attention to something you wrote though.  \r\n\r\n\u0026gt;mid level engineers spending lot of time arguing about things that should not be the focus of the code reviews - e. g. variable names, code styles etc. In doing so, they are also not paying enough attention to the overall architecture, correctness, maintainability, testability etc. for the code they are reviewing.\r\n\r\nThis is a false dichotomy.   Having code with well thought out names and formatting, *enables* having maintainable and testable code.  It makes reasoning about correctness much easier.  Same is true for the overall architecture.  I would go so far as to say, you cannot have all of the attributes you desire, without having code that is easy to read.  \r\n\r\nNow, mid level devs are notorious for taking \"Clean Code\" too far, and inciting holy wars to purge the heathen sinners who dont conform 100%.  Perhaps they just need their zealotry toned down.  Names and formatting are definitely important, but not so important that they cant see the forest for the trees.","subreddit_name":"ExperiencedDevs","author":"restlessapi"},{"body":"[Clean Code](https://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882) taught me how to write clean code. Cannot recommend this book enough, every place I've worked I've brought a copy and at least one coworker will borrow it and find themselves really questioning a lot of their decisions. It's also a great book to refer back to every few years.\r\n\r\nedit: Truthfully, some was experience, seeing other people's code early on. Discussing with peers. Thinking about single responsibility et cetera. I don't think there is one source but the book is something at the top of the list.","subreddit_name":"cscareerquestions","author":"chasenyc"},{"body":"[Clean Code by Bob Martin](https://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882/ref=sr_1_3?ie=UTF8\u0026amp;qid=1531067317\u0026amp;sr=8-3\u0026amp;keywords=clean+code)\r\n\r\nIt's written in Java, but for the most part, it's very transferable to C#. When I was a junior dev transitioning to intermediate, it was pretty worth my while. It's a relatively easy read and doesn't require you to be writing code or sitting at a computer (at least it didn't for me).\r\n\r\nFeel free though while reading it to critically question some ideas as to how applicable they are in the C#.NET ecosystem, current best practices, and your day-to-day work. (For example, IIRC, he argues that you shouldn't prefix interfaces with the capital `I`. I still do that though and I find it worthwhile.)","subreddit_name":"csharp","author":"FizixMan"},{"body":"Poorly written code generally doesn’t follow Best Practices, but includes issues like using inappropriate algorithms and data structures to manage data, and bad design decisions.\r\n\r\nI recommend Clean Code by Robert Martin https://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882\r\n\r\nHe does a great job of highlighting what makes code readable, and maintainable, especially in the context of Java and OO Design and OO Programming.\r\n\r\nI’ve heard some call it controversial. But after more than 20 years in the industry ( username relevant) I find him to be particularly on point and accurate. Personal preference aside, he knows what he is talking about and tells it like it is.","subreddit_name":"learnjava","author":"iamsooldithurts"},{"body":"La filosofia descritta da te riassume la filosofia \"all'italiana\" : si massimizza il guadagno, minimizzando l'investimento. Questo non solo in termini di economia, ma anche di tempo e, talvolta, di istruzione.\r\n\r\nPersonalmente penso e ho trovato aziende (anche piccole) che hanno metodi molto più rigorosi per lo sviluppo (creazione di documentazione secondo un certo stile, ogni variabile deve essere assegnata con un nome preciso, ecc..). Poi, vabbè, ci sono anche aziende molto grosse con la metodologia AGILE , ma già creare una buona documentazione e seguire poche e semplici regole , fa la differenza fra il buon \"programmatore\" e il mitico cuggino.\r\n\r\nUn buon libro per i colleghi [Clean code](https://www.amazon.it/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882) , sempre che di inglese ce ne capiscano qualcosa.","subreddit_name":"ItalyInformatica","author":"serhack"},{"body":"Write clean code that is easy to understand. Commenting is, at best, a necessary evil.\r\n\r\nTake this for example:\r\n    \r\n    if((employee.flags \u0026amp; HOURLY_FLAG_ \u0026amp;\u0026amp; employee.age \u0026gt; 50)\r\n        employee.GetBenefits()  \r\n\r\nvs.\r\n\r\n    if(employee.IsEligibleForFullBenefits())\r\n        employee.GetBenefits()  \r\n\r\nCode *can* be self documenting; but it takes good craftsmanship and a lot of experience to make it happen. \r\n\r\nI totally stole this example from the book [Clean Code](https://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882) and its chapter on commenting, but it really drove the point home for me. Worth a read for anyone who wants to craft well written applications.","subreddit_name":"Angular2","author":"boogermanus"},{"body":"The problem is that to understand clean code they have to be able to differentiate between good and bad design. That insight usually only comes with the experience of having to modify badly written code. I can point them to [Clean Code By Robert Martin](https://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882). But most of it will go over their heads.","subreddit_name":"learnprogramming","author":"EvasiveBeaver"},{"body":"Powers you say? Who needs powers to defeat Yandere Dev when you already have access to [the ultimate weapon](https://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882/ref=sr_1_1?dchild=1\u0026amp;keywords=clean+code\u0026amp;qid=1626046818\u0026amp;sr=8-1)...","subreddit_name":"Osana","author":"Euler-Angles"},{"body":"Other than the standard naming conventions I try to use the project standards when joining to an existing project. I also use the best practices from [Clean Code by Robert C. Martin](https://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882/), I could definitely recommend that one. Not only it mentions good naming conventions, but also other best practices.","subreddit_name":"java","author":"Hakky54"},{"body":"You can Google around for small tips here and there, but there's no substitute for sitting down and reading a few chapters of a great software engineering book.\r\n\r\nThe best book I have ever read on this topic is called [Clean Code](https://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882) by Robert Martin. I bought this book for every new hire in my software department and trained them on the principles of it. All agreed that it was the best level up for writing modular, maintainable, easy-to-understand code.","subreddit_name":"learnprogramming","author":"yourdeadneopet"},{"body":"I study computer science, 2nd year bacc degree, one more year to go. \r\nI have excellent grades, but I still wasnt able to study more subjects and finish two years in this year although I had right to do it by Uni's regulations. The rule says that excellent students have a right to listen more subjects and finish studies earlier. \r\nThey said they havent met anyone who wants to have more subjects in one year and although its great thing I am motivated, they cant accept my request because they arent informed enough. The reason why I did made request in first place was that I am pregnant with my first baby and it will hard for me to study and take care of baby at the same time. I dont know if I will be able to finish my studies next year, but I will try my best.\r\nI would really like to have this book so I can improve my coding skills and move out from this country so my baby doesnt have to live and learn in environment that demotivates you. \r\n\r\nhttps://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882/ref=pd_aw_fbt_img_2/141-1711604-2353620?_encoding=UTF8\u0026amp;pd_rd_i=0132350882\u0026amp;pd_rd_r=635ced9c-4021-46f6-9f0a-e38d7b41ff23\u0026amp;pd_rd_w=ZgAa7\u0026amp;pd_rd_wg=HDQCf\u0026amp;pf_rd_p=8ad921d8-8b3b-4c8e-be01-c425a146feba\u0026amp;pf_rd_r=57PNMF7YBG2X1V7SBREG\u0026amp;psc=1\u0026amp;refRID=57PNMF7YBG2X1V7SBREG","subreddit_name":"RandomKindness","author":"Opala24"},{"body":"It's a book/pdf. It's available for free with a little searching but I am on my phone so I'm just going to throw the amazon link your way so you can at least see what it is, who the author is etc...\r\n\r\nhttps://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882\r\n\r\n","subreddit_name":"learnjava","author":"crooks5001"},{"body":"No, it's not just about shortening syntax. Shortening syntax could be the opposite of clean code sometimes, like for example readability is more important than compact code in most cases. \r\n\r\nIt's about proper layering, error handling, naming, uniform formatting, testing and a lot more.\r\n\r\nHere is a good book about it https://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882","subreddit_name":"learnprogramming","author":"gramdel"},{"body":"There are a lot of great comments here talking about tooling and error handling which you should pay attention to. However writing tests, using CI/CD, writing error handling, etc. will only ensure that your code is correct. Correctness is necessary, but not sufficient for production code. \r\n\r\nProduction code is code written to be understood and by someone other than the person who wrote it. This includes things I’m sure you’ve heard such as comments, descriptive variable names, and doc strings, but it also encompasses how you approach writing code. \r\n\r\nHow detailed are your commit messages? Do you write descriptive PRs that explain why and how you are doing something? Are you taking the time generate formal documentation? Are you following the single responsibility principle? \r\n\r\nThe above is just a snippet. It’s a lot to learn, but that’s ok. No one expects you to know how it all. If you want to prod code, start practicing on your own. Write doc strings, write PR messages to yourself, make atomic commits. Go read [clean code](https://www.amazon.com/Clean-Code-Handbook-Software-Craftsmanship/dp/0132350882). There is a good reason it’s a classic. \r\n\r\nMost importantly though, you should practice writing code with people. You will grow much much faster if you get other people’s eyes on the things you write. If your team doesn’t do code reviews consider contributing to an open source project. Preferably a smaller one because the maintainers will have more time to devote to you. \r\n\r\nYou should also read as much code as you can. This will teach you things like convention, design patterns, appropriate levels of abstraction, etc.","subreddit_name":"datascience","author":"Aidtor"}]}