Testing is but a proxy to achieve the true goal, and is far from perfect.
Do you realize that this thread was about someone saying that debug builds are a legacy holdover from the 80s ?
Testing is but a proxy to achieve the true goal, and is far from perfect.
What is this supposed to mean?
Additionally most software runs as a service this day, so you have fast deployment iterations to collect errors.
Even for something like games, they get OTA updates all the time, fixing bugs that were only found while people were playing the game.
> What is this supposed to mean?
This is a pretty simple sentence in straightforward English. Which word do you have a problem with?
It argues that you shouldn't debug optimized builds.
Obviously, as I pointed out, a real programmer needs to be able to debug optimized builds.
Maybe you should be the one tracking what you're replying to.
What about just compiling and running your program after you make a change or get a crash?
Crashes in production happen with optimized builds. You need to be able to inspect the core and figure out what happened from there, as usually you can't reproduce the scenario.
Right... What's your point? This scenario doesn't overlap with regular iterations. Normal workflow and a crash after a program is distributed are two separate things.