So when someone offers to do something inherently dangerous on your behalf, you should be incredibly deliberate.
There's no shortage of frameworks, platforms and libraries that have been bit (repeatedly) by SQL injection.
Lets not pretend that Ruby/Rails doesn't make major architectural decisions in favour of ease of use for the user.
e.g. if HTTP params weren't automatically marshalled into non-string data structures this bug wouldn't exist.
This doesn't seem to be the case: fugu preparation is licensed and regulated, and deaths are very rare indeed. I can't find exact numbers offhand, but according to a paper cited on Japanese Wikipedia, there were 315 fugu poisoning incidents in Japan in the 10 years from 1996 to 2005. Of those, 31 were fatal, and of those, the majority were due to preparation by unqualified individuals (presumably those who had caught fugu themselves).
Given the quantity of fugu consumed nationwide, it seems reasonable to say that, in fact, most chefs never cut fugu wrong - or at least that most chefs never serve wrongly cut fugu.
https://ja.wikipedia.org/wiki/%E3%83%95%E3%82%B0#.E3.83.95.E...