Learning Program
How the program actually works
Most people who want to learn programming spend weeks looking for a starting point and never find one that fits how they think. This program was built around that exact problem - not around a fixed curriculum.
You choose between group sessions, where ideas develop through discussion, and private lessons, where a single instructor follows your pace. Both paths lead to the same practical fluency.
Whether you're coming in with zero background or you've tried coding before and stopped - the program places you where your understanding actually is, not where a syllabus assumes it should be.
What the structure looks like
Each stage of the program is designed to be completed independently - so if life interrupts, you don't lose your footing.
Instructors include professionals who've worked as a computer repair specialist, systems administrator, and software developer - people who understand what it means to troubleshoot real problems under pressure, not just teach syntax.
Imagine someone who spent years fixing other people's computers before deciding to learn how to build software instead. That's the kind of background many instructors here bring - grounded, practical, and genuinely useful when a student gets stuck.
Sessions run live, which means you can ask a question mid-explanation and get an answer before moving on. Recordings are available afterward, but the live format is where most learning happens - through the back-and-forth that recordings can't replicate.
Group cohorts meet twice weekly. Private sessions are scheduled around your availability.
Stages of the learning path
-
Foundations of computational thinking
Before writing a single line of code, you spend time understanding how computers interpret instructions. This stage uses plain-language exercises - no syntax yet, just logic patterns that carry through everything that follows.
-
First working programs in Python
Python is chosen deliberately - its readability means you spend less time fighting the language and more time learning what programs actually do. By the end of this stage, you've built four small tools that solve real problems you chose yourself.
-
Data, files, and working with the web
Programs rarely live in isolation. This stage covers reading from files, making web requests, and handling data that doesn't arrive in a clean format - the kind of work that defines most real programming jobs.
-
Capstone: building something of your own
The final stage is a project you define. Instructors guide the scope and review the code, but the idea and direction come from you. It becomes the first piece of work you can genuinely show to someone else.
Who the instructors are
Nadia Veltri started as a computer repair specialist - diagnosing hardware failures before she ever wrote an application. Tomasz Kędra spent six years in systems work before moving into software. They bring that same diagnostic mindset to teaching: when a student's code doesn't behave as expected, the first question is always "what did you expect it to do?" - not "what did you do wrong?"
That distinction matters more than it sounds. Students who learn to ask good questions about their own code stop depending on instructors much faster - and that independence is the actual goal of the program.
pcclean-usboost has been running this approach since 2024, refining it with each cohort.