Indeed he did say 'think' but he first stated his credentials so that what he thought had weight and authority and was therefore the truth. I replied in kind to stay the opposite. Both of us were guessing about the state of the code in exactly the same way that you are guessing about the state of their processes.
This is an assumption but not the only possible one. By saying 'all' you imply that this is the only one. There are many other possible assumptions that fit the observed game including the one that says "we assume that the risks, effort and priorities involved in fixing the bugs are such that they do not get fixed at this time". Picking on one negative assumption and implying that it is the only one and therefore correct is at best ignorant and at worst deliberate.
There is also the possible situation whereby the complex and non-deterministic nature of the game code results in wildly unpredictable results for small changes in the inputs. The so called 'butterfly wing effect' of Chaos Theory, meaning that fixing the bugs requires immense care and effort lest by doing so the results are worse than before.
But I'm only guessing.
The implication isn't that i'm saying that there is only one assumption, it implies that all assumptions fall into that one described. If the bugs are too hard to squash in a cost-benefit analysis, then the process is bad because they dont see the bugs as important as players do or the process allowed the bugs to become costly fixes in the first place. If the bugs are too hard to fix because the code is a spaghetti mess and nobody can follow the logic then the process setup to govern how the code is done on some level is broken. In all cases you can narrow things down to either a flaw in process or a lack of ability. Unless you think this is acceptable to deal with 2 years post release - which should be obvious that i dont.
The difference in view comes from a difference in expectation. I expect month long beta's (which come after their internal testing of code) to hammer out all the reported bugs the new features introduce before moving to release. I expect that because this is not listed as early access and it's 2 years post release.
Instead what we have is what you'd expect in an early access game. We have content integral to the core parts of the game getting introduced years after release because it's finally ready to be included, we have bugs, which often go unfixed for weeks and even months on the "production" client.
I got no problem changing my expectations for an early access title. It's not my fault fdev wants to market it as something more mature, and that comes with different expectations (or should). So I stand by...either something wrong with the process or something wrong with the talent. The bugs that have been left in post-beta and then not usually fixed for weeks is just not acceptable, doubly so with no real explanation given.