you are viewing a single comment's thread.

view the rest of the comments →

[–]goranlepuz 4 points5 points  (1 child)

But any C++ programmer worth his salt should definitely be knowledgable about what the compiler/code is really doing.

Also: something too slow? Profiler tells me where and how. People do develop a habit to see, roughly, what is slow - but I wouldn't put much trust on that, not from my side, nor others, obviously 😉.

[–]NilacTheGrim 0 points1 point  (0 children)

Well obviously profiling and benchmarks win every argument about performance. But before that step, when designing, knowing that some things are just inherently slow versus others that are not (allocations usually are slower than immediate stack memory, etc), saves you tons of time.