Excellent suggestion.
Sometimes when I come across something that is unnecessarily difficult or repetitious I wonder if the software developers use the software they create (because if they did they wouldn't have made it like that).
Regarding your comment about how the new body selection and velocity reset when you reload a system I imagine you may have thought that about me. 
LOL no worries, that one was an easy one to catch. Since when you're playing pool you fire and the balls go off into space, so you have to reset and quickly you get annoyed by having to repeatedly input the numbers.
Although you've probably noticed I'm a little different then the average user. I have a knack for design and usability when it comes to "how a thing should be done". It's something I've grown to discover over the years, my mind will automagically solve some problem giving me a general framework, and presents it to me as a series of images/animations. It basically gives me the overall plan, framework and 'map'. And it doesn't just apply to software either, right now I've got a design for a new mouse with some borrowed items from other hardware peripherals lol .... going to try to make a prototype and maybe get it made if I can find the right people, I've never done it before though.
Plus many "gotcha's" are merely a matter of not having enough time, one human being can't possibly know every possible combination by themselves, hence the necessity of feedback. A lot of dev's I notice don't like "criticism", when it is actually not criticism they should be afraid of, but software no one wants to use!
I have tremendous respect for software developers, I thought about writing an essay about software development to distill the wisdom I've picked up over the years just because I've dabbled in it and I have a lot of insight from both the user and developer perspective - just because many things in programming require SOO much time and work, just to get small things working. People have no idea just how much work is involved in some of the features, major or minor they suggest.
But there's another thing too - some features require a lot of effort for little financial gain (i.e. enormous money pit), therefore they have disproportionate ROI, even though the feature is something good and adds to the functionality. One thing I've learned is that --> good design goes against economic efficiency, the two are at odds, and hence a lot of bad engineering happens. All that is required for good design is time + skills, since overall good development is a function of time and feedback (i.e. blizzard entertainment and their games)
That's one thing the pointy haired bosses don't fully grasp, I've also told game developers that too --> That game development rubs right up agains the economic model we use as a society, just because the project is such a massive undertaking, and "figure out as you go". It's getting better but a lot of it just has to do with the enormous amount of work that has to go into creating tools and whatnot and unforseen obstacles. Hopefully as tools get better, and automatic content creation gets good enough, that game devs can focus more on the game, instead of the shiny new graphics with shader version x.0
I'll try to find the awesome video I saw a while back where blizzard was speaking to other game devs about software development, a lot of the wisdom in that video applies across the board to software development and engineering in general.
Topic: October Update Now Available (Read 6583 times)
