Earlier quoted context omitted.
The idea you have to pick between reasonable engineering and fun is a false dichotomy. Of course not every game will have the time budget to fix every unintended feature but your example game would have been more enjoyable (especially for the mentioned Playstation users) if the code had been written a bit better.
I think for games like Blue Prince, specifically, it’s not a false dichotomy. Those are made in tiny teams. You can either spend more time tinkering with the gameplay mechanics and experimenting with the game parts; or you can put on your software engineer hat and make the code better (or, spend even more time to learn how to make the code better in the first place!). This gets less true with scale of a team, and wit…
ID software once was a small team and they built complex games by writing tight code which was modular and very clear. Lots of their '3d era' contemporaries failed because their engines were sloppy, complicated, buggy and slow.