So, I did a count of "Confirmed" bugs. There are already over 100 in less than 1 week! Only a handful are marked fixed. (I'm lucky, one of my bugs got fixed).
Some are subtle, such as "difficulty in relocating buildings with extensions" or similar issues in buiding access where the adjoining road is curved.
But: Some are so obvious, such as "garbage incenerators don't collect any garbage" that this code should never have passed any kind of review.
My point is:
If casual users can find all these bugs, how deep is their defect database? Must be hundreds of known bugs at launch.
They should have not announced a launch date until beta testers were finding only minor issues.
I would get fired if I launched such a product.
Background: In the 80's I was a software manager of a game company. I now produce other kinds of software, that actually works. (it gets unit tested, tested by automation srcipts. manually tested and tested by other internal groups). If it has any major bugs, we don't ship it.
Some are subtle, such as "difficulty in relocating buildings with extensions" or similar issues in buiding access where the adjoining road is curved.
But: Some are so obvious, such as "garbage incenerators don't collect any garbage" that this code should never have passed any kind of review.
My point is:
If casual users can find all these bugs, how deep is their defect database? Must be hundreds of known bugs at launch.
They should have not announced a launch date until beta testers were finding only minor issues.
I would get fired if I launched such a product.
Background: In the 80's I was a software manager of a game company. I now produce other kinds of software, that actually works. (it gets unit tested, tested by automation srcipts. manually tested and tested by other internal groups). If it has any major bugs, we don't ship it.
- 8
- 1
- 1