Tom ForsythFeb 9, 2024
If your debug build is faster than 25% the speed of your release build, you're not doing enough debug checking. Buy your devs faster computers.
John KessenichFeb 9, 2024
Show threadTom Forsyth
Here's an old blog post on the subject. I stick by it:
https://tomforsyth1000.github.io/blog.wiki.html#%5B%5BLogging%2C%20asserts%20and%20unit%20tests%5D%5D
TomF's Tech Blog - It's only pretending to be a wiki.

Feb 9, 2024 at 8:59amWeb
Show threadAndre WeissflogFeb 9, 2024
@TomF I think you'll like my coding style :D (in that case I recommend to not include asserts in release builds though, but I should really use different levels of asserts for debug vs release).
Show threadAndre WeissflogFeb 9, 2024
@TomF in the past I've been much more hardcore about "ignorable asserts" though, when an assert hit it was always game-over and the responsible coder had to drop anything else and fix the problem. In a mid-sized game-dev team (up to 80 peeps or so), this worked pretty well. Might be a problem though on much bigger teams.
Show threadJosh SimmonsFeb 9, 2024
@floooh @TomF we don't have ignorable asserts unless you have a debugger attached. Works pretty well. We don't use asserts for asset validation, general rule is if it's a data problem it should never crash the engine. (Ofc this doesn't always work out but mostly it does)
Show threadTom ForsythFeb 9, 2024
@floooh Three thumbs up!