I'd love if SE could inform us some more about their general work behind the patches.
I've for example always wondered if it took them 3 years to notice people wanted split BP timers, or 3 years for them to notice the game needed split BP timers, or if the work and testing itself took 1+ years of testing and tweaking.
This would then make it easier to understand how they work, and why excellent ideas you run across on boards don't seem to be implemented. Other interesting things such information could tell is is how much something has to be suggested to be implemented. Is it enough with 1 email of a good idea, or do they just pile them up in sorted bunches until they've got 1000 of a certain idea before they even start to consider it?
In other words, it would be nice if SE could tell us the work behind patches, from suggestion sent in, or SE survey/reading of boards to implementation with time and workload estimated.
I've for example always wondered if it took them 3 years to notice people wanted split BP timers, or 3 years for them to notice the game needed split BP timers, or if the work and testing itself took 1+ years of testing and tweaking.
This would then make it easier to understand how they work, and why excellent ideas you run across on boards don't seem to be implemented. Other interesting things such information could tell is is how much something has to be suggested to be implemented. Is it enough with 1 email of a good idea, or do they just pile them up in sorted bunches until they've got 1000 of a certain idea before they even start to consider it?
In other words, it would be nice if SE could tell us the work behind patches, from suggestion sent in, or SE survey/reading of boards to implementation with time and workload estimated.
Comment