This latest book of John Sonmez is an admirable result of self-discipline. The product of an author/programmer who doesn't just preach about doing things, but he shows us the way by example. Maybe the form of his book is unconventional, but he wrote it in a way that would fit his ways of doing things.
One of our roundtable topics of our last French Riviera Craftsmanship Meetup was about collecting things that you shouldn't do to your newcomers as a manager. If you are just a developer, still, you shouldn't do them, but it is less likely anyway.
I like the books and most of the videos created by Uncle Bob. Maybe sometimes they are a bit too simplistic, but they help to provide a better understanding of how you should write good quality code. And if you find that a topic is not deeply analyzed enough, you can still explore it later on your own.
Are you the type of person who doesn't pay attention to details? Start using C++. It will give the missing discipline if there is any chance. If you don't pay attention to details, C++ will teach you to do it, or you will leave this language pretty soon. It simply does not tolerate ignorance and laziness. It will hit back when you expect it the least with bloating memory leaks and dramatic core dumps.
We are living in a world where anywhere you turn, someone will bark in your face how successful he or she is. How much he likes his life and that if you are not a zillionaire by the age of 30 you are nothing but a douchebag. Okay, this might sound like a little bit of exaggeration, but not that much to be honest.
In my new team we are working on several guidelines, rules and process improvements. Why do we think these are so important? If things are well documented, it's easier for a newcomer to start delivering value. It reduces the possibilities to err for everyone. It removes lots of possibilities for arguments. And we all know that one cannot win an argument, we should avoid them at all costs.