Every compilation tool I’ve ever used has a nifty little feature where if you have a syntax error, it’ll tell you what file, line number, type of issue (ex: expected semicolon), and will often even point a little arrow at the part of the line that produced the error. Sure, it might take a bit if you wrote hundreds of lines of code without running it even once, but even then it’s more of a slight hassle that you just need to work through to get to the actually difficult bugs. It’s a rare and pleasant day if the only bugs I encounter are syntax errors.

...magnetic? Gravity is?

Sorry about the nitpick, but syntax errors should not be the ones any decent programmer screams at. Syntax errors are the ‘you made a typo’ kind of error, and development editors generally highlight them as you type. Failed unit tests, segmentation faults or libraries with no documentation would be more realistic.