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

Work with JSON and XML Data

4 weeks · 2 milestones

Databases: Semistructured Data (Stanford on edX), 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

1–2 weeks (10 hrs/week)

Take Databases: Semistructured Data for free and do queries over real JSON and XML data, with their outputs. Keep everything in one public repo or notebook as you go. Certificates cost money. Audit is free; you never need the certificate here.

Proof required

Link your public repo or notebook with queries over real JSON and XML data, with their outputs, and a screenshot or log showing the self-check passed.

What gets checked

  • Data is real and its source is named.
  • Queries give the right output.
  • Each query says what question it answers.

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 queries over real JSON and XML data, with their outputs.

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: Do the free exercises; they check your queries.
  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: Databases: Semistructured Data (Stanford on edX)
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

  • Data is real and its source is named.
  • Queries give the right output.
  • Each query says what question it answers.
  • Ask one question about a choice in the code; the answer should be clear.

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

Turn messy JSON into answers

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

Use what you learned. Make a script that loads real JSON from a public API and answers three questions. Keep it small enough to finish in about two weeks.

Proof required

Link a script that loads real JSON from a public API and answers three questions, with a README that says how to run or read it.

What gets checked

  • It runs from the README.
  • Answers are right.
  • Bad records are handled.

Common mistakes

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

Powstik Guide

A script that loads real JSON from a public API and answers three questions.

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

  • It runs from the README.
  • Answers are right.
  • Bad records are handled.
  • Check that the work is the person's own.

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

Part of