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

Apply Ethics to Technology

11 weeks · 2 milestones

Ethics, Technology and Engineering (Santa Clara Markkula Center: Ethics in Technology Practice), 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

5–9 weeks (2 hrs/week)

Take Ethics, Technology and Engineering for free and do an ethics review of two real tech cases using the toolkit. Keep everything in one public repo or notebook as you go. OSSU lists a Coursera course. We use the free Markkula Center materials.

Proof required

Link your public repo or notebook with an ethics review of two real tech cases using the toolkit, and a screenshot or log showing the self-check passed.

What gets checked

  • Cases are real and named.
  • Each review uses the toolkit's steps.
  • Both sides are given fairly.

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 an ethics review of two real tech cases using the toolkit.

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: Work through two case studies with the toolkit, then compare notes with a friend.
  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: Ethics, Technology and Engineering (Santa Clara Markkula Center: Ethics in Technology Practice)
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

  • Cases are real and named.
  • Each review uses the toolkit's steps.
  • Both sides are given fairly.
  • Ask one question about a choice in the code; the answer should be clear.

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

Run an ethics check on your app

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

Use what you learned. Make an ethics review of a project you built, with one change you made because of it. Keep it small enough to finish in about two weeks.

Proof required

Link an ethics review of a project you built, with one change you made because of it, with a README that says how to run or read it.

What gets checked

  • The review is specific to the project.
  • The change is in the code or the docs.
  • People affected are named.

Common mistakes

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

Powstik Guide

An ethics review of a project you built, with one change you made because of it.

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 review is specific to the project.
  • The change is in the code or the docs.
  • People affected are named.
  • Check that the work is the person's own.

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

Part of