Free · No account · No ads

Learn programming step by step.
Become a developer who understands why.

A structured path from "what is a computer program" all the way to writing your own Laravel-like framework. PHP, OOP, SQL, MySQL, APIs and Laravel — every concept starts with the problem that made someone invent it.

  • 11 full lessons
  • 190+ sections
  • 0 assumed knowledge
Step 1

Choose your learning path

Eleven lessons are written and free to read right now. The rest are planned — they are marked, not hidden, so you can see where the path is going.

Being written next JavaScript HTML & CSS Git Real Projects Interview Prep
Step 2

The roadmap

Topics build on each other. Skipping ahead almost always means coming back — this is the order that avoids that.

  1. 1 Programming BasicsWhat a program actually is
  2. 2 Language HistoryWhy your tools exist
  3. 3 HTML & CSSStructure and layout
  4. 4 JavaScriptThe browser half
  5. 5 PHP & OOPThe big one β€” objects, SOLID
  6. 6 ComposerUsing other people’s code
  7. 7 Database BasicsHow data is really stored
  8. 8 SQL & MySQLJoins, indexes, transactions
  9. 9 APIsHow programs talk
  10. 10 Laravel DatabaseEloquent ↔ raw SQL
  11. 11 Build a FrameworkThe capstone
  12. 12 Real ProjectsShip something

Ready when you are

No sign-up, no email, no payment. Open the first lesson and start reading — your progress is saved in this browser automatically.

Start free
Why here

Written like a mentor, not a manual

Six things that are deliberately different from the documentation you have already read.

Problem before definition

No lesson opens with "a class is…". It opens with code that breaks, so the definition arrives as a relief rather than a rule to memorise.

Tied back to Laravel

Every concept ends by pointing at the exact place it appears in a real Laravel app β€” Contracts, the container, Eloquent, middleware.

Drawn, not just described

Diagrams, flowcharts and step-by-step execution traces. If an idea can be drawn, it is drawn.

Exercises with no answers

Three per lesson, easy to hard, with expected output and a hint β€” but never a solution. Reading a solution feels like learning and is not.

Interview questions built in

Thirteen per lesson at three levels, answers hidden until you have tried. Written the way a senior would actually answer.

Hinglish recap

Every lesson explains the whole topic again in plain Hinglish at the end, for when the English version did not quite land.

Inside a lesson

What every lesson contains

Not a wall of text with headings. Thirteen distinct parts, in the same order, every time — so you always know where to find the bit you need.

Learn Problem before definition
Visual diagram Every idea drawn
Flowcharts Mermaid, with a text version
Code examples Copy button on every block
Step-by-step run What PHP actually does
Notes and tips The things that catch people
Common mistakes And why they happen
Laravel connection Where it lives in a real app
Exercises Easy, medium, hard
Quiz Answers hidden
Interview questions Hidden answers, three levels
Cheat sheet One screen, everything
Hinglish recap The whole topic again, simply

See it before you commit

These are real screens from the lessons — the archival photographs in the history sections, and the diagrams that explain how data is stored. Click any image to open it full size.

Open a full lesson
ENIAC, 1945 β€” from the Language History lesson. The operators are the programming language.
IBM 729 tape drives β€” why sequential access made databases necessary.
The punched card that is why terminals are 80 characters wide.
The plan

From first line of code to job ready

Nobody becomes a developer by reading. This is the loop that actually works, and where each part of the site fits into it.

Start No account, no payment, no email
Learn Problem first, then the code
Practice Exercises with no answers given
Build A mini project per lesson
Projects Full applications, end to end
Interview Questions and answers per topic
Job ready You can explain, not just copy
How one lesson works
Text version
Real problem -> Definition -> Analogy -> Smallest code -> Line by line -> Internal execution -> Professional version -> Laravel connection -> Quiz + interview questions -> Exercises (no answers) -> Mini project
Straight answers

What this site is, and what it is not

What it is

  • A free, complete study path you can finish.
  • Written for someone who has never programmed.
  • Honest about what is finished and what is planned.
  • Yours to keep — progress stays in your browser, not on a server.

What it is not

  • Not a video course — everything is text you can search and scan.
  • Not a certificate mill. There is no badge at the end.
  • Not a replacement for the official docs — it is what makes them readable.
  • No student counts or testimonials, because there is nothing to count yet.
FAQ

Questions people actually ask

Yes. Every lesson is free to read β€” no account, no paywall, no email required.

No. Start at Programming Basics; it assumes you have never written a line of code. If you already program, start at PHP & OOP instead.

Documentation tells you what a feature does. These lessons start with the problem that made someone invent the feature, then show the code, then show exactly where it appears in a real Laravel application.

No. Bookmarks, reading progress and finished exercises are stored in your own browser. Nothing is uploaded and nothing is tracked.

Around 8 to 10 hours of reading. Actually absorbing it β€” doing the exercises and the mini projects β€” is closer to four to six weeks of evenings.

Build something. The Build a Framework lesson is the capstone for that reason: once you have written your own router, container and ORM, Laravel stops looking like magic.

Start with the very first question

"What actually happens between typing code and seeing a web page?" That is lesson one, and it assumes nothing at all.

Begin