Patterns can be classified in various ways. The most prominent ones are the ones used in the books “Design Patterns: Elements of Reusable Object-Oriented Software” and “Pattern-Oriented Software Architecture, Volume 1“.
Today, I want to present the five winners of the vouchers for my book “C++ Core Guidelines Explained: Best Practices for Modern C++”.
Training and mentoring aim one goal: to improve your skills in a well-defined way. Although both aim for the same goal, they use very different ways. One may fit your needs, but not the other.
I give away five vouchers for my book “C++ Core Guidelines Explained: Best Practices for Modern C++”. In return, I have a question about modern C++. Which feature in C++11/14/17 is the most influential for you and why?
Most software developers assume that the book “Design Patterns: Elements of Reusable Object-Oriented Software”, published in 1994, stands for the birth of patterns. No. The term was coined by Christopher Alexander in 1977.
Before I write about patterns in my upcoming posts, I have to answer one question first. What are the advantages of patterns? As you may assume, I see many advantages, but I boil them down to three points: well-defined terminology, improved documentation, and learning from the best.
Last week, the visitor numbers on this page went from 7,000/day to 25,000/day. Now, I know why. I’m nominated for the “2022 Business Worldwide CEO Awards”. You can still vote for me.
Based on my last poll, “Which mentoring program should I implement next?” I recognized that there is a significant demand for writing about “Design Patterns and Architectural Patterns with C++”. Today, I would like to present to you my plan for future posts.
Thanks to C++23, constructing containers will become more convenient. Additionally, the ranges library got more new views.
This Sunday, the poll for my next mentoring program ended. There is a unique winner: Design Patterns and Architectural Patterns with C++.