powstik
Prove
LiveProof-of-Work · Oct–Nov: every verified proof counts. 35 days leftAll outcomes
Skills

Design Larger Programs with Objects (Object-Oriented Design)

15 weeks · 2 milestones

Object-Oriented Design (Northeastern CS 3500), then one project of your own. Part of the Varsity Curriculum: Computer Science.

Milestone map

Milestone map

2 milestones

Do the course work in public

7–13 weeks (5–10 hrs/week)

Take Object-Oriented Design for free and do the course assignments (model, view, controller). Keep everything in one public repo or notebook as you go.

Proof required

Link your public repo or notebook with the course assignments (model, view, controller), and a screenshot or log showing the self-check passed.

What gets checked

  • Model, view and controller are separate.
  • Interfaces hide the details other parts should not see.
  • Tests cover the model and pass.

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 course assignments (model, view, controller).

Steps

  1. Make a public repo or notebook first.
  2. Do one unit at a time and commit after each.
  3. Run the self-check: Write the tests each assignment asks for first; they must pass.
  4. Write a short README: what is here and how to run it.
  5. Ask three people who know the topic to check it.

Template

README
Course: Object-Oriented Design (Northeastern CS 3500)
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

  • Model, view and controller are separate.
  • Interfaces hide the details other parts should not see.
  • Tests cover the model and pass.
  • 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 an app with a clean design

1–3 weeks (5–8 hrs/week)

Use what you learned. Make a desktop or command-line app split into model, view and controller, with a short design note. Keep it small enough to finish in about two weeks.

Proof required

Link a desktop or command-line app split into model, view and controller, with a short design note, with a README that says how to run or read it.

What gets checked

  • The design note matches the code.
  • You can swap the view without changing the model.
  • Tests pass.

Common mistakes

  • A project too big to finish.
  • A demo that only works on your machine.

Powstik Guide

A desktop or command-line app split into model, view and controller, with a short design note.

Steps

  1. Write one line: what it does and for whom.
  2. Build the smallest version that works.
  3. Test it on someone else's machine or with someone else reading it.
  4. Write the README.
  5. 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 design note matches the code.
  • You can swap the view without changing the model.
  • Tests pass.
  • Check that the work is the person's own.

You'll sign in first, then come straight back here.

Part of