Well, first and formost (especially after Radimus said "as an arts major, you should stick to asking if someone wants to supersize their meal."), know that IT people have a strange sense of humor. Assume we're teasing/busting first.
Second, write comments in your code - lots of them. In some of my larger projects, you will find up to 45% of the file is comment text! I usually can't remember what I had for breakfast by the second cup of coffee, so don't expect me to remember why I coded it that way 9 months ago!
Third, use meaningful variable names. Personally, I like to use CAPS for GLOBAL and MixedCase for Local var names. Find a general style you are comfortable with and stick with it. Look at other peoples code to see how it is laid out, decide what you like/don't like and adopt the best.
Fourth (should be first, but had to reference the others) - Never take Lonk's advice verbatim! (see - there's the sarcastic humor!) He'll tell you to use no comments, minimal spaces, no indents, and single-character var names! He covers the "Good" and "Ugly" parts of the "Good, Bad, and Ugly" trilogy, and codes everything for a KixGolf project! It's great code, if a bit uncomprehensible.
Finally, Richard's comments are right on target. Many of us write and even respond to questions in "pseudo-code" - a mix of code, logic, and descriptions of what we haven't yet decided how to code. It's a great way to organize your ideas, and pseudocode often becomes the comments in your code.
Welcome to the board..
Glenn
_________________________
Actually I
am a Rocket Scientist!
