Programming Assignment Tips
Read the brief first, plan before you code, and test as you go — habits that survive marking.
Programming assignments are marked not just on whether your code runs, but on how you got there — the logic, the structure and the decisions you can explain. The students who score highest treat the assignment like a small software project, not a typing race.
Read the brief before you write a line
Re-read the brief twice and pull out the hard requirements: inputs, outputs, constraints, file names, marking criteria. A program that solves the wrong problem perfectly earns nothing. Write the acceptance criteria in your own words and tick them off as you go.
Plan, then code in small steps
Sketch the solution as pseudocode or a flow diagram before opening an editor. Then build it in the smallest possible increments — one function, one feature — compiling and testing after every single step. Code written in one sitting is code that fails at the last minute.
- One task per function; if a function does two things, split it.
- Name variables for what they hold, not how you typed them.
- Test edge cases: empty input, negatives, one item, very large values.
- Write a tiny comment explaining why — not what the line obviously does.
Make sure it actually runs
The most common reason strong-looking code loses marks is that it does not run on the marker's machine. Check the input format your code expects matches the brief exactly, avoid environment-specific paths, and confirm your solution passes the sample inputs the brief provided before you submit.
Continue reading
The full guide on the original site