Teach programming without the marking pile
Write the exercise once, with the starter file and the tests that settle it. Every student gets the same setup, every attempt is marked the moment it arrives.
Checkout Calculator
4 students · 100 points available
| Student | Status | Score |
|---|---|---|
| Maya Chen | Passed | 100% |
| Sam Ortiz | Submitted | 80% |
| Priya Nair | In progress | Not yet |
| Diego Ramos | Not started | Not yet |
Running your class
The day to day work of setting exercises and seeing how they land.
Write the task once, give it to everyone
Instructions, a starter file and the tests that decide the mark. Some tests you show, some you keep back. Every student opens exactly the same thing.
The tests do the marking
Each submission runs in its own sandbox the moment it arrives. No copying files onto your machine, no running them one by one, no spreadsheet at the end of it.
One table for the whole class
Who has opened the work, who has handed it in, who passed and with what score. You can see the shape of the class in a glance, and who needs a nudge.
Deadlines that behave the way you expect
A soft deadline flags late work as overdue and lets it through. A hard one shuts the workspace when the clock runs out. You pick which one fits the task.
Helping them through it
Setting the work is the easy half. This is the other one.
Sit with a student who is not in the room
Open their file in a Cowork session and you are both in it — your cursor beside theirs, every change arriving as it is typed. Give them the code out loud or send a link. You can join to watch rather than edit, which is usually the right way round when somebody is thinking.
Read what they actually wrote
A submission is not just a score. Open it and you get the file as they handed it in, which test failed and what it expected — the difference between marking work and understanding where somebody went wrong.
One link, no roster
Hand out a link for a single assignment or a whole folder. Whoever follows it has the work in their list. Nothing to import, no class list to build before the first lesson.
Keep the handouts with the work
Attach slides, a worksheet or a reference link to a folder and it travels with the tasks. Students stop asking which system the notes were in.
Check in from a phone
Who has handed in, who has not, and what a student wrote — readable on a phone between lessons. Writing assignments is still a job for a keyboard.
A room with bad wifi
The desktop version keeps the assignments and the work on the computer and runs them with the Python or Java already installed there. Finished work goes out when the connection comes back, in the order it was done.
Bring your course to Snipcode
Start with one exercise and see how it marks. Build the rest when you are convinced.
Create an account