The most common web development mistakes students make are working without version control, leaving deployment until the deadline, hardcoding paths and secrets, ignoring mobile layouts and accessibility, and never testing outside their own machine — all avoidable with habits that take minutes to adopt.
1. No version control until it is too late
The classic failure story is a broken project the night before a deadline with no way back. Committing early and often — even to a private repository — turns disasters into a five-minute rollback, and Git history is increasingly part of how group contributions are assessed.
2. Deploying at the deadline, not from week one
Code that works locally routinely breaks in production: case-sensitive paths, missing modules, database connection settings. Students who deploy from the first week find these problems when they are small; students who deploy on submission day find them all at once.
3. Hardcoded paths, URLs and secrets
Absolute local paths (C:/Users/…), localhost URLs and database passwords committed into code are the three most common portability failures. Relative paths and configuration kept out of source control are habits worth forming in the first term — secrets in a public repository are a security incident, not just a lost mark.
4. Designing for one screen
Markers open student sites on laptops, phones and lab machines. A layout tested only at one window size falls apart in assessment exactly as it would in front of a client. Browser dev tools make responsive checking a thirty-second habit.
5. Ignoring accessibility basics
Alt text, heading structure, colour contrast and keyboard access are marking-scheme staples because they are professional-practice staples. They cost little during the build and are painful to retrofit.
For lecturers: environment consistency prevents half of these
Many of these mistakes thrive in inconsistent environments. When every student works on identical, institution-provided hosting with real deployment from week one, the deployment and portability lessons happen naturally — and marking happens against live URLs rather than zip files.
