Skillnaija Start free

Your First Programs, for a Group You Know

The capstone project for Coding Foundations: Think Like a Programmer — a free Data & Tech course. Pass it and you earn a certificate anyone can verify.

Start the course free Download the project workbook

The project unlocks once you complete the lessons. The workbook is free to download now so you can see exactly what is expected.

What you will submit

One link: a public GitHub repository (preferred) with your code files and a README, or a Google Doc set so that anyone with the link can view it, with your code pasted in. It must show the description of your group, the three functions, a screenshot of your checks printing PASS, screenshots of the page giving an answer and giving the message for an empty box, the bug log and the AI note.

What to do, step by step

  1. Choose a real group you know that shares money or takes turns: an ajo or esusu, a class or estate dues list, a football team's subscriptions, a church or mosque rota, a shop's credit book. It must not be the course's Kaduna ajo club with the names changed: use your own group's amount and rule, and invent the names (never put real phone numbers or other personal details in your code). Describe the group in two or three sentences at the top of your README or document.
  2. Part 1. Three functions, each shown running on your sample data in the Console or on a page: (a) a totals function, such as the amount collected so far and the amount still owed for the year; (b) a turns function that returns whose turn it is for a given week or meeting number, goes round the list again after the last person, and returns a plain message for a number below 1; (c) a function that takes an array of records with a paid (or done) flag and returns the names of those who have not paid, sorted alphabetically.
  3. Part 2. Checks: a check function like the one in Lesson 12 and at least six checks whose expected answers you worked out by hand first, including zero, an empty list and a number past the end of the list. Show them all printing PASS.
  4. Part 3. A page: one HTML file with an input, a button and an output area. Pressing the button reads the input, calls your functions and shows the answer with textContent, never innerHTML. An empty box, 0 or 2.5 shows a plain message on the page instead of a wrong answer.
  5. Part 4. A bug log: three bugs you met while building (at least one crash and one wrong answer), each with the exact error message or wrong output quoted, what you thought it was, what it really was, and the fix.
  6. Part 5. An honest AI note: which parts an AI assistant helped with (or that none did), one thing it got wrong or that you had to change, and how you checked. Using an assistant is allowed; hiding it, or submitting code you cannot explain, is not.

Files to work with

Project workbook (fill in, then submit)The whole brief, an evidence checklist, the grading rubric as a self-check and the link-sharing steps in one file. Opens in Word, Google Docs or WPS.Word · 7 KB

How it is graded

CriterionWeight
The three functions are correct on the learner's own sample data and on the edge cases: zero, an empty list and a number past the end of the list28%
At least six checks with answers worked out by hand, shown printing PASS12%
The page reads the input, calls the functions, shows the result with textContent, and answers bad input with a plain message20%
The code is readable and the learner's own: clear names, small functions, no repeated blocks, their own group rather than the course's ajo club14%
The bug log shows real debugging: exact messages or outputs, the wrong guess, the true cause and the fix16%
The honest AI note is specific and shows the output was checked10%

You need 65% overall to pass. A failed submission comes back with feedback and can be revised and resubmitted once free; further attempts come with the All-Access Pass or as a paid retake.

Before you submit: make your link public

If your work lives in Google Drive or Google Docs, open Share → General access and change “Restricted” to “Anyone with the link” (Viewer). Then paste the link into a private browser window: if it opens without sign-in, you are ready. A private link cannot be graded — it is the single most common reason a good project fails.

Frequently asked questions

Do I have to finish Coding Foundations: Think Like a Programmer before submitting the project?

Yes. The submission screen opens once every lesson in Coding Foundations: Think Like a Programmer is marked complete. The lessons are where the methods, the local context and the worked examples the project depends on are taught.

How is the project graded?

An examiner scores each rubric criterion from 0 to 100 and weights them as shown on this page; you need 65% overall to pass. Most submissions are graded within minutes and you get written feedback on what was strong and what to improve.

Can I resubmit if I fail?

Yes. A failed project comes back with feedback; revise the weak parts and resubmit. A passed project is final — the certificate is issued and cannot be re-rolled.

What do I actually submit?

A write-up of what you did (under 5,000 characters) plus a public link to your work — a Google Drive folder, Google Doc, spreadsheet, GitHub repository or video. The link must open without sign-in; a private link cannot be graded. The free project workbook on this page walks you through all 6 steps.

Is the certificate real?

Yes. Passing this project issues a certificate with a unique verification code. Anyone — an employer, a client, a school — can open the verification page and see that the certificate is genuine and which project earned it.

More Data & Tech projects

Ready to earn this certificate?

Coding Foundations: Think Like a Programmer is self-paced. Finish the lessons, complete this project, and the certificate is yours to share.

Start learning free