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

Build Software Like a Team Does

8 weeks · 2 milestones

Software Engineering: Introduction (UBC CPSC 310 (free materials on GitHub)), 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

3–6 weeks (8–10 hrs/week)

Take Software Engineering: Introduction for free and do a project built the course's way: user stories, tests first, pull requests, CI. Keep everything in one public repo or notebook as you go.

Proof required

Link your public repo or notebook with a project built the course's way: user stories, tests first, pull requests, CI, and a screenshot or log showing the self-check passed.

What gets checked

  • Tests run in CI and pass.
  • Pull requests show review.
  • User stories match what was built.

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 a project built the course's way: user stories, tests first, pull requests, CI.

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: Every change must pass your tests in CI before it merges.
  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: Software Engineering: Introduction (UBC CPSC 310 (free materials on GitHub))
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

  • Tests run in CI and pass.
  • Pull requests show review.
  • User stories match what was built.
  • Ask one question about a choice in the code; the answer should be clear.

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

Ship a change to an open-source project

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

Use what you learned. Make a merged pull request to a real open-source project. Keep it small enough to finish in about two weeks.

Proof required

Link a merged pull request to a real open-source project, with a README that says how to run or read it.

What gets checked

  • The PR is merged.
  • It has tests or docs.
  • You answered reviewer comments.

Common mistakes

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

Powstik Guide

A merged pull request to a real open-source project.

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 PR is merged.
  • It has tests or docs.
  • You answered reviewer comments.
  • Check that the work is the person's own.

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

Part of