DAE change their mind on SAST tools after chasing one SQL injection bug for 9 hours?
I always figured running Semgrep was a waste since I could just read the code myself, but after burning 9 hours in San Jose hunting a blind SQLi in a Django view that a 4 second scan flagged in the f-string on line 112, I'm not so sure anymore.