Code Reviews – What? (Part 2)
Now that we know good reasons to do code reviews, which parts of our code need to be reviewed? What does not need review?
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 […]
A few days ago, I attended the Meeting C++ conference in Berlin, the third year in a row. As usual, I had a lot of fun and interesting conversations with […]
The mutable keyword seems to be one of the less known corners of C++. Yet it can be very useful, or even unavoidable if you want to write const-correct code […]
In the last days, I’ve played around with Cevelop a bit, mainly interested in the refactoring capabilities it offers.
Code smells are indicators that there might be something afoul in our code. Here is a list of some of the most important smells.
I recently got an email, asking me how I approach an unknown code base. Here’s an answer.
Whenever you start something that will be “work in progress” for some time, take some sufficiently detailed notes.
Last week I have touched source file organization of generated code. Today I’ll share some thoughts on testability of code when a part of it is generated.
It’s time to write about project file organization again (See part 1 and part 2). Recently I came across two cases of confusion concerning dependencies and generated code that, in […]