Milestone map
Milestone map
2 milestones
Do the course work in public
7–14 weeks (5–20 hrs/week)
Take Java Programming for free and do the exercises in parts 1–14. Keep everything in one public repo or notebook as you go.
Proof required
Link your public repo or notebook with the exercises in parts 1–14, and a screenshot or log showing the self-check passed.
What gets checked
- The TMC points page shows the exercises passed.
- Code is in a public repo with real history.
- Classes and methods are small and well named.
Common mistakes
- Copying posted answers: verifiers read the history.
- Skipping the self-check, then asking for review too early.
Powstik Guide
A public repo or notebook with the exercises in parts 1–14.
Steps
- Make a public repo or notebook first.
- Do one unit at a time and commit after each.
- Run the self-check: Install the TMC plugin; each exercise has tests that run when you submit it.
- Write a short README: what is here and how to run it.
- Ask three people who know the topic to check it.
Template
README Course: Java Programming (MOOC.fi (Helsinki)) What is here: How to run it: Self-check result: What was hardest:
What gets sent back
- No history, just one big upload.
- Self-check not shown.
- Code that does not run from the README.
Resources
Foundationstart here
Depthgo deeper
What a verifier looks for
- The TMC points page shows the exercises passed.
- Code is in a public repo with real history.
- Classes and methods are small and well named.
- Ask one question about a choice in the code; the answer should be clear.
You'll sign in first, then come straight back here.
Build a Java app with tests
1–3 weeks (5–8 hrs/week)
Use what you learned. Make a small Java program (a to-do list, a grade book, a text game) with classes, a saved file and JUnit tests. Keep it small enough to finish in about two weeks.
Proof required
Link a small Java program (a to-do list, a grade book, a text game) with classes, a saved file and JUnit tests, with a README that says how to run or read it.
What gets checked
- It runs from the README.
- JUnit tests pass.
- Data is saved and loaded from a file.
Common mistakes
- A project too big to finish.
- A demo that only works on your machine.
Powstik Guide
A small Java program (a to-do list, a grade book, a text game) with classes, a saved file and JUnit tests.
Steps
- Write one line: what it does and for whom.
- Build the smallest version that works.
- Test it on someone else's machine or with someone else reading it.
- Write the README.
- Ask three people to check it.
Template
README What it does: Who it is for: How to run it: What I would do next:
What gets sent back
- Does not run from the README.
- Not clearly the person's own work.
- Claims more than it does.
Resources
Foundationstart here
Depthgo deeper
What a verifier looks for
- It runs from the README.
- JUnit tests pass.
- Data is saved and loaded from a file.
- Check that the work is the person's own.
You'll sign in first, then come straight back here.