This gives you a lot of credit. Something that "you" don't always deserve :-)
A more modern approach to software development is to ask the users to tell you stories about how they intend to use the product. Then you the developer translate that into the how/what/etc in a more free and less restricted way.
Basically you treat the users as if they are idiots and children :-)
With this intro I reckon this thread will be a hive of activity LOL (read no one will post) although, the "xyz for dummies" books sure took off didn't they??!!
Here is a link or two on user stories :
http://www.agilemodeling.com/artifacts/userStory.htm
http://en.wikipedia.org/wiki/User_story
So, I guess I (being an idiot) better kick this off :
OK, so perhaps that was more than one story, but they are pretty closely related. Instead of giving Aaron the freedom to do what the hell he wanted on this front, I asked for a big red button. This got the job done and quickly, but not necesarily in the best possible way. Describing what I wanted rather than how to achieve it would have afforded him more freedom in how to achieve it even if the basic tools for the job are the same 3 packet sequences no matter what. The code and GUI in between could be almost anything :-)Fred The Idiot wrote:I want to be able to switch between serial monitor mode and FreeEMs mode without turning off the ignition of the car. I also want to be able to reset the FreeEMS to make it pick up changes to flash only config without turning off the key. Sometimes I want a reset to pick up the serial monitor switch and sometimes I don't.
Right, your turn, tell us some tuning stories, preferably very short unlike my poor example.
I'll start a thread next to this for the developer(s) to ask you details of your stories such that this one remains pure and uncluttered :
Place your comments and questions about the stories below in here!
Fred.