Had first an interesting discussion if you can call the “patterns” we use patterns. Or if there are no “patterns” in software-development, just “idioms”. Of course, quite academical question.
But it reminded me to remove the dust & spider-webs from my own knowledge and refresh it a bit. What’s better than doing it with some C++17 – support?
The other book was just referenced in some software architecture-book. Interesting collection of anecdotes. I can confirm half of the given examples as “seen in real life and projects” ..
Reading some developer-news lead to a quite interesting and practical brochure 840 pages) about software-testing in general and in regard to C++:
The first glimpses about methodical, mutation-based test-case selection, (..) were interesting. Because fully comprehensive tests are (even with automation) not doable.
Will report after I have finished reading it – stay tuned.
edit 20180501: A bit disappointed, because I expected more. More content and more in-depth hints. In the end it looks just like the excerpt of one or two chapters of the book. Yes, it fans the flames for “more”, but … it looks like a cheap appetizer.