It is a good read, definitely in the top 10, but I would not say it is THE BOOK, and also I would not recommend it for junior developers that are in their first 2 years of programming (as in they have bigger fish/books to fry).
I read it at the start of my second year and I'd actually agree with that. The book is amazing and will definitely improve how you write code, but the examples are written by an experienced Java programmer and some of them are quite hard to understand for beginners.
If you do decide to read it, don't be afraid to stick to the topics that seem relevant and skip ahead here and there (as I did). It's a great book to come back to after some time has passed and the appendix/summaries at the end are very helpful.
There’s surely a lot to learn, but juniors are actually able to learn a lot in a short amount of time.
Moreover, “common sense” doesn’t really count. That sounds like not allowing children to try something only because one think they won’t make it.
So for me, clean code next to testing is one of the foundations of high quality code and I’ll start teaching that as early as possible.
We do coding dojo’s every sprint so we actually practice what we preach :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
It is a good read, definitely in the top 10, but I would not say it is THE BOOK, and also I would not recommend it for junior developers that are in their first 2 years of programming (as in they have bigger fish/books to fry).
Which one do you suggest instead ?
Learning to code first, then you can understand the "rules" and how/when to break them.
None, I think is specific, because every dev has its own gaps and knowledge.
For example Clean Code and Clean Coder goes hand in hand, covering complementary skills.
Before these the Pragmatic Programmer may clear the way into explaining what devs actually do.
There are 2 posts on dev.to with top 10, I think we can start from there, but all are equal important.
I read it at the start of my second year and I'd actually agree with that. The book is amazing and will definitely improve how you write code, but the examples are written by an experienced Java programmer and some of them are quite hard to understand for beginners.
If you do decide to read it, don't be afraid to stick to the topics that seem relevant and skip ahead here and there (as I did). It's a great book to come back to after some time has passed and the appendix/summaries at the end are very helpful.
Hmm, interesting. Actually it’s among my personal top 3 of influential books and I’ll have every new developer read it in my team.
I read it when I was already an experienced developer. It was more about giving things names and good example that already did out of a gut feeling.
But I haven’t thought about how it it is received by inexperienced developers...
Is it just your feeling or do you have tales to people that actually had problems understanding it?
I did not tried to test it on juniors, it is common sense I guess.
It solves issues they do not encountered yet, do not understand so they will not apreciate.
They have bigger fish to fry: a language, paradigms, dev tools, how software works in general and how is developed and so on.
There’s surely a lot to learn, but juniors are actually able to learn a lot in a short amount of time.
Moreover, “common sense” doesn’t really count. That sounds like not allowing children to try something only because one think they won’t make it.
So for me, clean code next to testing is one of the foundations of high quality code and I’ll start teaching that as early as possible.
We do coding dojo’s every sprint so we actually practice what we preach :)