Just like you chose to ignore all my counterpoints above?
Completely irrelevant to an end-user. My understanding of the backend has absolutely no bearing on my expectations as a consumer. People should not be saying oh its ok Yoshi, we know you have spaghetti code to deal with. Not our problem, it's his job to identify solutions and implement them in meaningful and timely ways regardless of the challenge.being in the programming field you should know the amount of time and testing it takes to implement things that seem like nothing to the consumer, however can take time on the back end. I'm surprised this has note ven crossed your mind.
No. I am expecting the devs to actually use their brains the first time around they design their content to make sure its actually:Like any other game phases / patches are meant to implement changes based on feed back. What your suggesting is for people to give it 100% percent, and then come up with more creative solutions later on which in turn can burn out creative minds and make them work harder rather than at a steady step that would be comfortable to the staff.
1) Fun
2) Well designed
3) Scalable
We keep getting features that not only miss a mark, but often multiple/all. Then they can FURTHER iterate on pain points, or if there are limited pain points, they can IMPROVE/expand the content.
The problem is that they're constantly fixing existing content because it just isn't well designed, fun, or scalable. It severely limits their ability to design new content, let alone GOOD new content. Not only that, but we're also riding an incredibly rigid content development template that is getting stale.