[derefr]

Just because the person didn't know enough about the domain to use the correct terminology is no reason to belittle them by thinking they "want to do something stupid," though (and yes, that's why they're angry); half of software engineering is figuring out what the heck people mean with their requirements, and the usual best first assumption, no matter who your client/student is, is that they want to do something cool :)

I like to give anyone who asks me to teach them "to make games" or anything similar this test first, though: I take a pen and put it down on a page of paper, and tell them to tell me to draw a happy face on it, without expecting me to know what a happy face, or even a circle, is. I take everything they say literally, and tell them "this is how the computer would react to that." Clears up any misconceptions pretty quickly. :)

[amalcon]

My problem is that people often think you're trying to belittle them when you're just trying to figure out what they want to do. Maybe this is because people do belittle each other for not knowing proper terminology. It still causes problems.

I have had people ask me "how do you program DOS", when they were in fact looking for (among other things):

- How do I write a batch file (easy to explain)

- How do I make a simple console program (slightly tougher, but I could at least point them in the right direction, or show them if they are willing to take the time)

- How do I program my calculator to do trigonometry for me (This was my absolute favorite one, because I could actually show them the basics on the spot! Back in the day, I showed a few people how to do this, who actually turned out to really enjoy doing it!)

- How do I make a game (this is the worst one)