Time is time. We tend to think it’s simple to deal with it. But it’s more complex than it sounds. Both in programming and in real life. You want to measure how long something took, add a timestamp...

I planned to finish this series this week. But then I realized that there are still a couple of important things about testing that I haven’t written about yet. We already touched on the problem of...

In the earlier parts of this series, we explored the foundations of <chrono>: durations, time points, clock selection, inter-clock conversions, and even custom clocks. Click here to access al...

In earlier articles of this series, we walked through the foundations of <chrono>, explored the essential clocks (system_clock, steady_clock, high_resolution_clock), and even looked at the ex...

In this series, we’ve already talked about the main pillars behind <chrono>, the most widely used clocks, and even inter-clock conversions. Those clocks — system_clock, steady_clock, and hig...

It’s the end of another year, and as I’ve done many times before, I’m sharing a personal reflection on how the year went: what I achieved, where I fell short, and what I’m planning for the next one...

By now in this series, we’ve spent time looking at the major standard clocks and their behavior. We’ve talked about wall-clock time, monotonic clocks, and the myths around “high resolution”. Today,...

This year I had the chance to attend three conferences onsite, plus one online, and even a meetup in my hometown, Budapest. Depending on who you ask, maybe it’s not a lot — I know some speakers do ...

If there’s one clock in <chrono> that causes the most confusion, it’s std::chrono::high_resolution_clock. The name sounds too tempting — who wouldn’t want “the highest resolution”? But like m...

In the previous articles, we explored what clocks are in general and took a closer look at std::chrono::system_clock, the one that represents the wall-clock or calendar time. Now let’s move to anot...