3 ms·
Maybe they were new 15 years ago in Rails, but I was using them in Perl in the mid-90s. There is no excuse for writing an SQL injection in 2021. Zero. None. An
by kstrauser 6y ago
Maybe they were new 15 years ago in Rails, but I was using them in Perl in the mid-90s.
There is no excuse for writing an SQL injection in 2021. Zero. None. And if you're in the position to write code that'll be deployed to production, you darn well better have it reviewed by peers before it's merged.
If the CTO did this and worked around the developers, he's a freaking idiot. If the engineers saw this and signed off because he's the CTO, they're freaking idiots. I wouldn't ordinarily be this harsh about it, but come on. SQL injections in 2021? That's astoundingly bad.
- rsynnott 6y ago> Maybe they were new 15 years ago in Rails That's when Rails came out :) I'm fairly sure ActiveRecord has always supported them.
- dragonwriter 6y ago> Maybe they were new 15 years ago in Rails, Well, Rails was < 2 years old then, so everything was new in Rails.
- ratsmack 6y agoI would think a Ruby code fuzzer would have caught something like that... if they have used one.