Milestone map
Milestone map
3 milestones
Set up and solve days 1–7
1 week (30–60 min/day)
Set up a clean repository. Solve the first seven puzzles in any language you like. Keep a short note per day on your approach. Early days are warm-ups; the habit of committing daily starts here.
Proof required
Link a public repository with solutions for days 1–7 committed on or near each day, plus a screenshot of your Advent of Code stats page.
What gets checked
- Solutions committed day by day, not in one batch
- Each day has a one-paragraph approach note
- Puzzle inputs are not committed
Common mistakes
- Committing puzzle inputs, which the rules ask you not to share
- Copying solutions from others
- Skipping notes
Powstik Guide
Days 1–7 solved, committed and explained.
Steps
- Create a repo with one folder per day.
- Gitignore your puzzle inputs.
- Read the rules on sharing and AI use.
- Solve, commit, then write a short approach note.
Template
Day NN — title Approach: Data structure used: Time complexity: What tripped me up:
What gets sent back
- Puzzle inputs committed.
- All days committed at once.
- No approach notes.
Resources
Foundationstart here
What a verifier looks for
- Check commit dates
- Check inputs are gitignored
- Read two approach notes
You'll sign in first, then come straight back here.
Push through days 8–18
11 days (1–2 hrs/day)
Keep going through the middle days, where puzzles get much harder. When stuck, write down what you tried before looking for hints. Getting through this stretch is the real test of the event.
Proof required
Link commits for days 8–18 with approach notes, and mark any day where you used a hint and what you learned from it.
What gets checked
- All days 8–18 solved with notes
- Hints disclosed honestly
- Notes show a technique learned, not just the answer
Common mistakes
- Quitting at the first very hard day
- Pasting a solution without understanding it
- Hiding hint use
Powstik Guide
Days 8–18 solved with honest notes.
Steps
- Timebox each attempt before looking for hints.
- Write what you tried when stuck.
- If you use a hint, rewrite the solution yourself.
- Note the technique each hard day taught you.
Template
Stuck log Day: What I tried: Hint used? yes / no — source: Technique learned:
What gets sent back
- Undisclosed hints.
- Copied solutions.
- Missing days.
Resources
Foundationstart here
Depthgo deeper
What a verifier looks for
- Check notes for techniques learned
- Check hint disclosures
- Pick one day and ask how it works
You'll sign in first, then come straight back here.
Finish all 25 and write a retrospective
1–2 weeks
Solve days 19–25 and collect all 50 stars. Write a retrospective on the techniques you used and what you'd do differently. The retrospective turns a month of puzzles into lasting skill.
Proof required
Submit a screenshot of all 50 stars for one year, the repository link, and a retrospective (400+ words) listing the techniques used and your hardest day.
What gets checked
- All 50 stars in a single year
- Retrospective names specific algorithms
- Honest account of the hardest day
Common mistakes
- Stars spread across different years
- A retrospective that lists days, not techniques
- Solutions missing from the repo
Powstik Guide
All 50 stars and a technique retrospective.
Steps
- Finish the last seven days.
- Group every day by the technique it needed.
- Pick your hardest day and explain why.
- Note what you'd practise before next year.
Template
Retrospective | Technique | Days used | |-----------|-----------| Hardest day and why: What I'd practise next:
What gets sent back
- Stars from more than one year.
- No technique list.
- Missing solutions.
Resources
Foundationstart here
Depthgo deeper
What a verifier looks for
- Check the stats screenshot matches the repo year
- Read the techniques list
- Ask about the hardest day
You'll sign in first, then come straight back here.