Which Book by Robert.c.martin Should You Read First
The Ane volume every programmer MUST read!
Superpower
Let'due south face it, united states of america developers alive in a very strange world. Explicate what you practice to 95% of the population and they'll likely glaze over before you lot've finished your sentence. What you practice with a calculator day-to-twenty-four hour period looks like bloody wizardry to most people, and so it should, programming is a superpower.
It is a superpower that needs careful idea and consideration, particularly for those programmers who are going to take to read your lawmaking later.
Always lawmaking as if the person who ends up maintaining your code is a violent psychopath who knows where you lot live.
The one volume I wish every programmer earlier me had read before writing that 3000 line office is Clean Code - Robert C. Martin.
Why Clean Code
This book gave me a whole new perspective, it has restructured the way I recall about each line of code. It made me realise that there is an art to being a software engineer.
It teaches:
- How to identify bad code
- How to meaningfully name variables/classes/functions
- How to write clean, small, unmarried-purpose functions
- When to comment, or rather, when non to annotate
- Guidelines to formatting code properly
- Using objects and data structures for appropriate data abstraction
- How to properly follow the laws of TDD and write make clean tests
- Elegant ways to handle errors
- Countless refactoring tips
- 67 smells and heuristics (Yes, I counted.🤣)
And much, much more.
Whenever I'k programming I have Clean Lawmaking an arms achieve away equally a reference. The book has tonnes of examples of transforming bad lawmaking to clean lawmaking and the pace by step process on how to become at that place.
For case, just the other day I was refactoring a role which violated the unmarried responsibleness principle on numerous counts and was scratching my head on how to split up it up properly. I consulted the volume to jog my memory on an efficient way to get nigh the process and there was an example exactly like my problem, the only minor difference really being the context.
Uncle Bob
Robert C. Martin (Commonly known as Uncle Bob) is a programming superstar. Not only does he write admittedly brilliant books he is also a very talented speaker. Just YouTube "Uncle Bob" and you'll detect a stream of talks he's washed, each of them as interesting as the next.
His web log is also one of my favourites to read with some pretty authentic quotes:
"Anybody who thinks they can get faster by not writing tests is smoking some pretty serious shit" - Robert C. Martin @unclebobmartin
ten:15 AM - 08 Aug 2019
Finally
In my stance, every developer should read this book, at to the lowest degree three times 😄. Information technology'll give you a whole new love for programming. You'll actually begin to understand when yous're writing bad code. You lot'll look at your sometime code and wince at its structure, the vertical spacing, the complication, the out of sync abstractions, the useless comments, and the spaghetti nature. (well, I do, every-single-day). In the volume, the code snippets are in Java merely the same rules utilise to most languages!
This web log is simply a brief introduction to the benefits of reading this book, I strongly recommend you have a read if y'all haven't already. I'd love to hear your thoughts on Clean Code and potentially how information technology changed your perspective. I'd also dear to hear of some other books which take completely contradistinct the way yous look at lawmaking.
Follow me on twitter if you don't want to miss out on absolutely brilliant programming insight: 🤣 @luke_garrigan
Read next
Design Systems for Developers
Kathryn Grayson Nanz -
Build a Video Briefing App from Scratch using WebRTC,Websocket,PHP +JS Day 44
ben pobi -
Athwart To Do app with Angular Forms - part 2
Lorenzo Zarantonello -
What Nosotros Dear About Spider web Development
Mikhail Karan -
Which Book by Robert.c.martin Should You Read First
Source: https://dev.to/lukegarrigan/the-one-book-every-developer-must-read-33p9