The thing is, the bugs manifest in many different ways. Sometimes you get ramp&drop, sometimes you get on-off flicker, there are a wide variety of things that can happen. Take a look at the graphs from Nanex - lots of different things are happening. I realize that to an outsider they may all look like "graphs going wonky", but similarly all computer bugs look like "omfg I just want my email" to a marketer.

It's not a programming language issue - it's a math issue that would happen in any programming language. Whether you use Python or Haskell, you'll run into problems if you call SOLVE(A,x) on an ill conditioned matrix A. So you cook up a special routine that works well for most of the inputs you expect to see and it screws up for the tiny fraction of cases where you get a bad matrix.

Throwing money and a team of devs won't get around this. Similarly, you can't put together a team of crack devs (each earning $500k/year) and ask them to solve the CAP Theorem in 6 months. All you can do is choose your tradeoffs and hope that most of the time your network puts you on the good side of those tradeoffs.