Learn Method and rubric

A short lesson, then the work.

No lecture theatre, no attendance register. Every week ends with something you built and someone who read it.

[01] The weekly shape

Five movements, repeated.

The same shape runs for six months. What changes is the size of the problem, not the method.

[01]

Lesson

A twenty to thirty minute explanation of one idea. Recorded, so you can rewatch it.

[02]

Guided exercise

You write the code during the session while a mentor watches the file and corrects it live.

[03]

Lab

A task you finish on your own against a written rubric. No time limit beyond the week.

[04]

Review

A mentor reads your code or your layout and writes what is wrong and what to change.

[05]

Demonstration

You walk through the work, answer questions, and write a short reflection on what you would do differently.

[02] Assessment

What the mark is made of.

Final rubric before admissions
Dimension Weight Evidence used What is not counted
Conceptual understanding 20% Quizzes, oral explanations and short written responses. Attendance
Practical assignments 30% Individual work, marked against a written rubric. Speed
Projects 30% Functionality, quality, originality, documentation and iteration. Hours logged
Communication and collaboration 10% Peer work, presentations and technical writing. Participation points
Final demonstration 10% A live walkthrough, questions and a short reflection. Bonus tasks

The weights are proposed. The final rubric is published on this page before applications open, and does not change during the cohort.

[03] Academic integrity

Your work, attributed.

You will use code written by other people. That is normal. Passing it off as your own is not.

Copying
Using a library, a snippet or a tutorial is allowed when the source is stated in the repository.
Presenting
The final demonstration is individual. A team may build the project; you present your own part.
AI assistance
Allowed for explanation and boilerplate. Not allowed for a lab answer submitted as your own reasoning.
Plagiarism
Submitting someone else's work ends the assessment for that task, with a written reason.
Appeals
An integrity decision can be appealed in writing. The appeal is reviewed by someone not involved in the original decision.
[04] Where this is going

Stage 01

Not yet offered

Foundation

Programming, web, data and the tools of the trade. Six months, one cohort.

Stage 02

Not yet offered

Specialisation

One school in depth: AI, client work, marketing or business.

Stage 03

Not yet offered

Industry and product

A long project with a real user and a real deadline.

This is a direction, not an offer. None of the three stages is open for admission. Nothing here is described as equivalent to a degree, and no stage will be until a specific programme is assessed and recognised by the relevant authority.

The Software Engineering pilot is the only programme with a published plan and an admissions route.

Read the programme