Milestone map
Milestone map
2 milestones
Do the course work in public
2–4 weeks (2–5 hrs/week)
Take Software Architecture for free and do architecture diagrams of two open-source systems from the book, drawn from their real code. Keep everything in one public repo or notebook as you go. OSSU lists a Coursera course. We use the free AOSA book instead.
Proof required
Link your public repo or notebook with architecture diagrams of two open-source systems from the book, drawn from their real code, and a screenshot or log showing the self-check passed.
What gets checked
- Diagrams name real modules from the code.
- Each diagram shows how data flows.
- The trade-offs named match the chapter and the code.
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 architecture diagrams of two open-source systems from the book, drawn from their real code.
Steps
- Make a public repo or notebook first.
- Do one unit at a time and commit after each.
- Run the self-check: Draw the system from the code first, then check your drawing against the chapter.
- 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: Software Architecture (The Architecture of Open Source Applications (free book)) 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
- Diagrams name real modules from the code.
- Each diagram shows how data flows.
- The trade-offs named match the chapter and the code.
- Ask one question about a choice in the code; the answer should be clear.
You'll sign in first, then come straight back here.
Write an architecture note for your code
1–3 weeks (5–8 hrs/week)
Use what you learned. Make an architecture note (diagram, parts, trade-offs) for a program you built, plus one change it led you to make. Keep it small enough to finish in about two weeks.
Proof required
Link an architecture note (diagram, parts, trade-offs) for a program you built, plus one change it led you to make, with a README that says how to run or read it.
What gets checked
- The diagram matches the code.
- At least two trade-offs are named honestly.
- The change is in the commit history.
Common mistakes
- A project too big to finish.
- A demo that only works on your machine.
Powstik Guide
An architecture note (diagram, parts, trade-offs) for a program you built, plus one change it led you to make.
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
- The diagram matches the code.
- At least two trade-offs are named honestly.
- The change is in the commit history.
- Check that the work is the person's own.
You'll sign in first, then come straight back here.