As promised in the last post about CMake, today we’ll use a proper CMake project structure for our “Hello CMake” project.
Last week, we’ve started our little CMake project with a “Hello CMake” one-liner. Now it’s time to expand that example by adding another target and information about the project.
Since I have mentioned CMake in a handful of past blog posts, it is time to give a short introduction for those that don’t know it yet.
I have written about the code style of having “trailing return types everywhere” in the past. My advice back then was to use them only when necessary. I might have […]
Today’s guest post is by Saurabh Hooda. Saurabh is one of the co-founders of hackr.io. You can find Saurabh on Twitter and Medium. image source C++ is, hands down, one […]
Doing code reviews means interacting with other humans, which we need to take into account. We also often have the luxury of being able to choose the reviewer, and the […]
We finally come to the core post of this series – how to do code reviews.
The “how” part of this post about code reviews got rather long, so I had to split it into two parts. This part is about preparing our code and our […]
Now that we know good reasons to do code reviews, which parts of our code need to be reviewed? What does not need review?
Are you doing code reviews with your current team? Do you feel they help a lot or are they just a waste of time? In part 1 of this blog […]