The Legacy Code Programmer’s Toolbox is the quite fresh e-book of Jonathan Boccara, the person behind Fluent C++.
Not surprisingly it’s about how to attack legacy code. The author gives practical examples of how we should digest such code and make it better for good. He doesn’t just propose to make any legacy code better, but to decide which parts are worth to change.
There is an e-mail from the Daily Stoic I go back to read frequently. I try to go back to it every time someone irritates me - so quite frequently. In that mail there is a quote from Anthony de Mello: “The question to ask is not, ‘What’s wrong with this person?’ but ‘What does this irritation tell me about myself?’”
In his book called Drive: The Surprising Truth What Motivates us the author Daniel H. Pink leads us through the history of motivating people starting from what he calls Motivation 1.0 up to release 3.0.
Oh, singletons… We can’t live with them, we can’t live without them.
I remember that in my first team there was a guy with a very bright mind, but he was not yet mature enough just after the university and in all the questions he was way too much opinionated and a bit too smug. Typical to most of us at the beginning of our career, isn’t it?
Why is it that #CleanCode is still the exception and not the norm in so many companies?
A very interesting question from Marcus Biel, who was the Director of Developer Experience at RedHat at that time posted on LinkedIn. That moment, I didn’t have the time to go deep on this topic, but I reread the answers a couple of months later.
Never split the difference is a great book on negotiations by a former international hostage negotiator from FBI. Christopher Voss shows us through various stories how and why hostage negotiation strategies changed over time at FBI where he was both a lead and an instructor. While at many points I felt that he was sharing stories with a too vehement pride - maybe it’s more a cultural thing - ha also shared big failures.