AmouAI Hub/Courses /Programming Fundamentals
A taught 100-hour course delivered asynchronously. Twenty-five days, each one two two-hour videos paired with an interactive module whose exercises check themselves the moment you submit. Python first — variables through object-oriented design — then Java as a second lens on the same ideas. No prior programming experience assumed.
Nothing to install. Python runs inside the page, and your code never leaves your machine.
Five learning outcomes. Every day in the syllabus below maps to at least one of them, and the projects assess them directly.
The same rhythm every day, so it becomes a habit rather than a decision. Videos are chaptered and the module links back to the exact timestamp when you need it.
New material, heavy on live coding. Mistakes are made and fixed on camera on purpose.
120 minWork the sections the video covered. Visualisers you operate, plus a real Python interpreter in the page.
≈45 minDeeper and applied: worked problems, the common traps, and a full program built end to end.
120 minWarm-up, core and challenge problems, graded instantly with feedback that tells you what is wrong.
≈45 minFive weeks, five days each. Days marked Ready are live now; the rest are being produced in order. Open any week to see its days.
Each day names the chapters to read. The modules stand alone if you do not have the books yet, but the reading is where the depth is.
No. Every module runs a real Python interpreter inside the page, so you can write and run code on day one with nothing but a browser. Day 1 also walks you through installing Python and VS Code properly, because you will want a real editor before long — but that is not a blocker to starting.
No. Python is compiled to WebAssembly and runs entirely on your machine. Nothing you type is uploaded, and there is no account to create. Your progress is stored in this browser's local storage — which also means clearing site data will reset it, and your progress does not follow you to another device.
Because the second language is what turns knowledge into understanding. In Python you learn what a class is; in Java you find out which parts of that were the idea and which were just Python's way of spelling it. Static typing, compilation and interfaces are hard to appreciate until you have lived without them.
Python comes first and gets fifteen days, so that only one hard thing is being learned at a time. Java arrives on Day 16 as a new set of rules for ideas you already own.
Yes. Everything is asynchronous and nothing expires. Four hours a day for twenty-five days is the intended pace, but two hours a day for fifty days covers exactly the same ground. What does not work is skipping the exercises to move faster — that reliably produces someone who can follow along and cannot write anything alone.
Each exercise carries a hidden set of checks that run against your code the moment you submit. Crucially, they re-run your code with different data — so an answer that hardcodes the expected result will fail, and an answer that actually solves the problem will pass.
Feedback is written to teach rather than to score: instead of incorrect you
get something closer to a score of 89 should be a B, you gave a C — check your branch
order.
Two directions. Data Structures and Algorithms is the natural next step if you want to get better at programming itself — thirty chapters on what to reach for and what it costs, with every structure animated. Or go to the ML courses: LM Playground builds a language model from scratch, and Diffusion Playground builds an image generator. Day 25 also maps the through-line into NumPy, pandas and the object-oriented design that every ML framework is built on.