Maybe you have been there, maybe you’ll get into a similar situation soon. Maybe you don’t work for the type of company where this could ever happen. Yet, most of us at least heard about highly knowledgeable, so-called senior developers who spend most of their time outside coding. Let’s put it in another way, they go to the office and they don’t do what they are best in.
I’m not a Java developer - anymore - yet I find that a big part of this book can be useful for any junior programmer. Maybe not only for them, as the book has elements that are always useful to be reminded to. In addition, it gives you ideas on how and what to teach to less experienced people.
Helping is important in life. You help the weak to get stronger, you help the hungry to learn fishing, you help someone to achieve her goals. Why not help your compiler to perform some optimization? As always, help benefits both the one that helps and the one that received a hand.
A good way to help the C++ compiler is to declare whatever variable const that should not change. It requires little effort, right?
I have a long list of books to read. I think I need some improvements to that catalog. After I finished reading The Rational Optimist I’m going to present you now, I questioned myself from where I got the inspiration to read it? How did I learn about it?
I’ve recently had the chance to attend an advanced Python course. I was really waiting for those three days. By the end of it, my enthusiasm waned. Why? Was the teacher not knowledgeable enough? Was he just not a good presenter?
Usually, I write about one single book in a given article, but this is a peculiar occasion. Last months I read both books written by Adam Tornhill: Your Code as a Crime Scene (YCCS) and Software Design X-Rays (SDXR).