Foundations
Algorithm kata
Even numbers, primes, palindromes, anagrams, substring search — documented in Markdown with diagrams beside the code.
A modern classroom for internet applications: diagrams before syntax, tools over dogma, collaboration over isolation — and a real career path beyond the grade book.
// philosophy
Years of class materials show a simple belief: students show up for themselves. The room is a workshop, not a trap. Curiosity beats compliance.
“You can copy code — but why would you? You’re here for your future, not for a checkbox.”classroom principle · career over grade theater
// craft
Backend roots, web surfaces, data, and the modern delivery toolkit — aimed at vocational IT qualifications and real product work.
HTML, CSS, PHP, JavaScript, databases, full request–response thinking, and project structure that survives a demo.
Loops, conditions, functions, palindromes, primes, sorting, string search — written as thinking exercises, not trivia.
Git, GitHub, terminal, Markdown, Docker compose, CI/CD intuition — the everyday craft of shipping software.
Practice exams, mock sessions, and large archives of vocational sheets — skills aligned with real certification goals.
Blogs, to-do apps, collaborative repos, pair reviews — code that has to live with other humans.
Innovation challenges, mobility recommendations, school web platforms — education that talks to the outside world.
// journey
Course materials walk a clear arc: environment → thinking → language → projects → exam readiness.
Editor, version control, local server, terminal — the workspace becomes a second home before the first loop is written.
Pseudocode and visual flow. If you can’t draw it, you don’t understand it yet — and that’s fine, that’s the lesson.
Same algorithm, different syntax. Students keep ownership of their stack while sharing a common problem set.
Auth, CRUD, layouts, databases, Dockerized demos — from first PHP scripts to multi-file team applications.
Mock vocational exams on a schedule, with feedback loops — calm preparation instead of last-minute panic.
// culture
Explicit classroom rules from course intros: the internet is allowed, curiosity is expected, and help is a feature — not a bug.
// studio
Across cohorts: personal intros on GitHub, shared apps, exam dry-runs, and experiments that look like junior work — on purpose.
Even numbers, primes, palindromes, anagrams, substring search — documented in Markdown with diagrams beside the code.
Sessions, forms, MySQL, multi-page PHP, CSS systems, team repos — software that remembers users and deadlines.
Compose files, volumes, static and dynamic services — demystifying “it works on my machine.”
Recurring practice windows with real-style sheets — HTML, CSS, PHP, SQL under time and rubric pressure.
From interactive teaching toys to layout challenges — code that explains itself when you press “run.”
Public-facing education sites, event forums, innovation contests — learning that leaves the lab network.
// profile
Teaching is grounded in long hands-on experience as a product-minded backend builder and architect — then translated into steps beginners can climb.
Structure, boundaries, and maintainability — not just “make the page green.” Students learn why folders and contracts matter.
PHP and JS/TS as daily languages; Linux and containers as natural habitat; delivery pipelines as a habit of mind.
Scope, iteration, and presenting work. Projects are more than homework — they are small product cycles.
The subject is framed around professional life after school. Grades are feedback; growth is the product.
Not a slogan about a semester score — a quiet bet on people who learn to think clearly, use modern tools without fear, and help the person next to them.
Follow me on X