1. Submitting Code Working > Not Working In almost all cases

2. Working Imperfect but working code beats broken programs – Code that fails to compile worth 50% at most

3. Read the Spec Write a program that reads in values for hourly pay and hours worked… Yes:No: Enter hourly pay:Enter hours worked: Enter hours worked:Enter hourly pay:

4. Extras If you want to show off: – Better not ask for extra input – Better not affect "normal" run of program Can always show me experiments in person

5. Emergency procedure Submit program that mostly does what it is supposed to – Handle as much of problem as you can – Work in small chunks!!! Comment out broken code – Leave it in to show what you tried

6. Style Counts Code can work but still be bad – Follow conventions for White space Naming Etc… – Write clean, concise, self-documenting code

7. Renaming Files Rename files inside QT creator: If you change filename in Windows, QT Creator will get confused

8. Checklist Did I name my file(s) correctly? – Spelling/capitalization count!!! Did I add the comment to the top of each file – My Name – What project this is for Does it work with official environment – Must compile with GCC (QT Creator) without modification