I believe there were suggestions and not mandates. All very solid ideas.
English
-
Yeah sorry to clarify - the tonality of the message/list is a bit abrasive, and the proposed solutions (while directionally I agree with them) are just untested ideas that distract from the more meaningful message. When with trying to consolidate the feedback of a userbase, developers, and executives, messages that come across as "Do XYZ" and don't really explain WHY you want XYZ to be done lose value. It's just not as effective at eliciting the change as you want as highlighting the actual problem you're trying to solve, and letting the experts (systems designers, devs, etc.) find good solutions. It's pretty clear the desired goal that the author is trying to get across, but if i'm on the sandbox team and asked my team member who read this article "Hey what was the video that got upvoted a lot about?" and he said "It's TLDR go back to D1 settings", well that's not the resolution we're all hoping the team comes away with. I know the above sounds 'lazy', but it's a reality in development. There are literally hundreds of thousands of voices stating what they want / think is best. It's not the community's job to 'fix' the issue, but it is our job to highlight the challenges we see with the project and WHY we don't like them. That's where problem solving starts.