In this next part of the big STL algorithm tutorial, we will discover only one algorithm, the transform. I find very important, plus it doesn’t have variants like the copy or move algorithms. On the other hand, it has two quite distinct constructors. Let’s check them one by one.
The last one of the Five good emperors, Marcus Aurelius had a note in his Meditations: “If you seek tranquillity, do less.” This is one of his thoughts that is the most applicable to software development.
How many times did you break the code and had you no idea what went wrong? How many changes did you introduce? Would it have been different if you had introduced only one change?
Smartcuts covers how to stimulate - mostly - professional development. Hence its subtitle is How Hackers, Innovators and Icons Accelerate Success.
By example, the author Shane Snow analyzes how certain successful people move seemingly faster to the top than others. And while there is no overnight success, you have to work hard to be among the best, there are ways to stand out and to arrive at the top a bit faster.
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?