So I get this question from an un-named source via MSN: Lets call her Amy for so we can keep track of it...: The undisclosed party involved wanted me to point out that this was a reasonable reason for this questions around the QA process which to give her, I mean the undisclosed party credit is true.

Amy says:
what's it called where you have an app accept only the first command sent to it and ignore any others for a set period of time? the intent is that you can't make it blow up by "button mashing"

David Kelley (Microsoft Robotics.NET) says:
?

David Kelley (Microsoft Robotics.NET) says:
bad programming

Amy says:
LMAO

David Kelley (Microsoft Robotics.NET) says:
or

David Kelley (Microsoft Robotics.NET) says:
an undocumented 'feature'

David Kelley (Microsoft Robotics.NET) says:
it depends on who wrote the program

sooo... the conversation kind of went on to talk about why we wouldn't want a feature. I mean really would we 'WANT' to write the code to slow down an application even more when reading the keyboard input buffer??? We have enough performance problems for building apps then to make them slow on purpose and just because our TV is slow doesn't mean we should make our computer slow... In any case, unless something like this is really, Really, REALLY, R E A L L Y important I would not go there... and if our app blows up then we should just deal with it... new concept here... 'Error Handling' [gasp].