Flav wrote on Jun 18
th, 2015 at 2:36pm:
Concurency Development : put in operation something that is field tested and barely out of prototype stage... and then play catch up.
Think they'll try that on the space programs?
It sounds very glib, and I'm sure it is appropriate in some industries under some circumstances (where the risks are low and theoretical testing is not effective). Mining is an industry that tends to do it. You can spend 12 months doing bench testing and theoretical modelling, but sometimes it's quicker to isolate an area and try something different and assess how it worked.
Some do, some don't.
In software development, it is not a prudent approach.
Once you lose a customer due to dissatisfaction, it is hard to get them back.
To the bean counters and shiny pants, it would sound great - faster development times, "free" beta testing and less accountability (everyone else is doing it). But shit product really does make you look unprofessional. It all comes down to Turdbine's belief in customer retention is short so therefore quality doesn't matter as they will leave anyway. Self-fulfilling behaviour.
Most reasonable people are tolerant and a few non game breaking glitches like string table errors are going to get thru - but most devs who take pride in their work swing back and fix most of the known bugs in the first hotfix. The devs I know hate the idea that their work has errors or is substandard.
I guess the Turdbine employees mostly don't GAF or aren't allowed to GAF by their leader.
Turdbine just seem to pick and choose what suits them to fix when they like, with no weight given to the impact on players/customers.