Software taught as product building.
Learners ship something people can use. They design an interface, build the logic behind it, store data, connect an API and put it on the internet, and learn to read and fix code as they go.
What learners get good at.
Six capabilities, built through projects rather than slides.
Foundations
HTML, CSS and JavaScript, and thinking in small, testable pieces.
Interfaces that work
Layout, responsiveness and design decisions that serve users on a phone first.
Backend and data
Servers, databases and APIs: where data lives and how it moves.
Connecting to hardware
Dashboards and apps that read from and control real devices.
Version control and teamwork
Git, code review and working in a team without overwriting each other.
Deployment
Putting a product online, monitoring it and fixing it when it breaks.
The learning path.
Every course follows the same five-step rhythm.
Build a page
Start with a real page for a real purpose.
Add logic
Forms, state and rules.
Add data
A database and an API behind it.
Connect a device
Show live data from a sensor.
Launch
Deploy, share and gather feedback.
What gets built.
Learners choose and shape their projects, with a coach to guide the engineering. These are common starting points.
- Who it is for
- Learners aged roughly 10 to 25. Entry level is set per cohort; ask us where your child or team should start.
- Format
- Cohort-based, hands-on, project-led. In person at the USCO lab in Ikeja, in schools, or virtual where the subject allows.
- Class shape
- Small groups of around five learners per coach in the lab, so everyone touches the hardware.
- Tools
- A laptop and the free tools we set up together in the first session
- Dates and fees
- Set per cohort. Message us for the current schedule; we reply within one working day.
“Make something you can explain, repair and improve.”
That sentence is the test every project has to pass before a learner presents it.