See my blog stats and thoughts for the first half of the year. The Story   Keeping things short I’d like to point out a few major things that happened in the first half of 2017: Moved to a weekly schedule! I was usually writing every second week, but then I’ve experimented with a weekly schedule… and it worked out quite nicely!

With each C++ standard, we aim for simpler, cleaner and more expressive code. C++17 offers several “big” language features that should make our code nicer. Let’s have a look. Intro   You might say that most of the new language features (not to mention The Standard Library improvements) are there to write simpler/cleaner code.

With around 230 positive reviews (85% of five stars) (4.7 on the average), John Sonmez made a huge splash when he published his first book “Soft Skills”. 2.5 years later we get another book. Can the new book continue his success? Can it move you further along with your? Bonuses today: giveaway and little Q&A with John.

“C++ Attributes… what?” There were almost 40% votes like that in my recent Twitter survey. Maybe It would be good to introduce that little-known feature? There’s even a good occasion, as in C++17 we’ll get even more useful stuff connected with attributes. Interested? Intro   Have you ever used __declspec, __attribute or #pragma directives in your code?

Is C++ well suited for writing fast small utilities/tools? Let’s see: For my recent giveaway I needed a tool that would take an input file - CSV with data and then draw a few winners from all of the entries. To make things more complicated each entry might have a different weight.

For C++17 everyone wanted to have concepts, and as you know, we didn’t get them. But does it mean C++17 doesn’t improve templates/template meta-programming? Far from that! In my opinion, we get excellent features. Read more for details. Intro   Do you work a lot with templates and meta-programming? With C++17 we get a few nice improvements: some are quite small, but also there are notable features as well!

In May 2017 we got one more book about Modern C++! A Few weeks ago I got a copy from Packt Publishing, and today I’d like to write a few words about the book. In short: it’s a very good book! :) But let’s see what’s inside… The Book   < a href=“http://amzn.

The second part of my series about C++17 details. Today I’d like to focus on features that clarify some tricky parts of the language. For example copy elision and expression evaluation order. Intro   You all know this… C++ is a very complex language, and some (or most? :)) parts are quite confusing.

The new C++ Standard - C++17 - is near the end to be accepted and published. There’s already a working draft, and not that long ago it went to the final ISO balloting. It’s a good occasion to learn and understand what are the new features. Let’s start slowly, and today we’ll look at language/library fixes and removed elements.

How does your typical coding session in Visual Studio look like? What’s the first thing you do when you’re about to start coding? Yes… let’s check Gmail, Youtube, Reddit, etc… :) OK, please be more professional! So, let’s assume my Visual Studio (2013, 2015 or 2017) is already started. What to do next?

As you might notice from reading this blog, I love doing performance optimizations. Let’s take some algorithm or some part of the app, understand it and then improve, so it works 5x… or 100x faster! Doesn’t that sound awesome? I hope that you answered “Yes” to the question in the introduction.

When doing my last performance tests for bool packing, I got strange results sometimes. It appeared that one constant generated different results than the other. Why was that? Let’s have a quick look at branching performance. The problem   Just to recall (first part, second part) I wanted to pack eight booleans (results of a condition) into one byte, 1 bit per condition result.