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 :)
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.