But he's not unfounded in his claims. The Head of Renault PU development at the tests admitted that they were behind schedule and is mainly due to software gremlins. Saying things like 'limp home' mode and 'fail safe' programs either didn't exist yet or were very immature in their development, even for relatively minor issues these then become major problems for the teams.
The problem is not that he's claiming there were software problems; there have been. It's with his pig-ignorant frothing about the causes of those problems.
Let's start with his opening passage
I’ve been working in the IT business since the mid-nineties and a recurring problem in recent years has been that even magna cum laude university graduates don’t know how to program properly anymore
Gosh! Really? Fresh-faced graduates aren't top flight programmers! Who'd have thought? A degree in Computer Science, at best, makes you a passable programmer; to become a good programmer you need experience. It has always been thus and it will always be thus. It's just ignorant to think you're saying anything insightful by commenting on this.
If you come fresh out of university today, chances are that you have learned to program in Java or C#, which has nothing to do whatsoever with programming. Imagine you were asked to write a program for bolting stuff together. Today’s kids would come up with something like that:
Translation: I'm a grumpy old fart who doesn't like this new fangled technology. It's also deeply irrelevant to the problems of Red Bull because you can bed your bottom socks that (a) they aren't putting fresh faced graduates straight onto the coalface and (b) the people they're hiring are embedded programmers not Java monkeys.
Renault, however, seem to have hired an unholy bunch of C# script kiddies or some guys, who acquired their hardware programming skills on Wikipedia, because if they were hardcore nerds from days gone by, we wouldn’t have heard the words ‘software problem’ uttered nearly as often as we did during winter-testing. To put it bluntly: A program that after 2 years of development still doesn’t run properly has been written by someone, who chose the wrong job.
Clueless speculation followed by a complete ignorance of development cycles. Astonishingly so from someone who claims to have been "working in the IT business since the mid-nineties". Red Bull's programmers aren't running towards a fixed target, they're constantly re-designing, re-developing and tuning towards hardware that changes on a weekly or even daily basis.
Testing these days is considered optional. When was it last time that you bought a video game that didn’t install a first patch within a week of release day?
Another clue-free comment. Games these days receive more testing than they ever have. The reasons that Games are coming out needing patches is because they're multiple orders of magnitude more complicated than they used to be combined with a bunch of economic factors and the fact that you
can patch these days. Did you know that Pac Man famously had a bug in its Ghost AI? In fact, test-driven development is vastly more widespread than ten years ago and barely existed twenty years ago, claims that bugs are down to second rate developers and - worse - down to programmers learning in modern languages are the purest rose-tinted nostalgia.
The last program I bought that didn’t need patching to repair basic functionality cost me 0,00 bucks, because I had written it myself. I had spent 3 months on programming it and 2 months on testing it and when it it was released, it worked. Today’s industry would have released it after 3 months and then spend 4 months on releasing patches that should have been part of the release version.
A spot of ego-stroking followed a failure to understand release cycles. More to the point: Renault
didn't choose the release date; they
couldn't hold back the software for further testing.
There's nothing insightful about pointing out that having software problems means you had problems in your software development means you had problems in your software development department but there's not a single solid insight in this blogpost; it's a collection of rants based on little more than arrogance and prejudice.