About
PYLI5 — short for “Python Like I’m 5” — teaches Python in plain English: explain each idea simply first, then show the real code behind it, then let you practise it in the browser. The mission is to take people from their first print() to writing small, genuinely useful programs, without hype or jargon.
Why PYLI5 exists
Most Python resources either assume you already think like a programmer or bury a simple idea under terminology. PYLI5 is for the people in between — beginners who feel overwhelmed by jargon and just want a clear explanation, a working example, and a reason the concept matters. Each lesson starts with a plain-English version, adds the precise technical version, and then gives you something runnable to try.
Who created PYLI5
PYLI5 is created by Grant Abell, a security engineer who uses Python day to day for practical automation, reporting, CSV handling, and tooling. That background shapes the site: lessons focus on plain-English explanations, working examples, and small projects that show how Python is actually used outside of toy problems.
The goal isn’t to make Python sound more complicated than it is. It’s to explain each idea plainly first, then show the real code behind it.
How lessons are written
Every lesson follows the same shape: a simple explanation, then the technical detail, then a runnable example you can edit and run right in your browser. Examples are kept intentionally small at first and grow more practical as you progress. Code is reviewed for clarity and tested for correctness, and the projects are built around real tasks — cleaning a CSV, organising files, calling an API — rather than abstract exercises.
What makes PYLI5 different
- Plain-English first, jargon second — never the other way around.
- Runnable examples in the browser, with no install and no account required for the core learning content.
- A focus on practical, useful scripts, not just syntax drills.
- Written for learners first, not for search engines.
Corrections and feedback
PYLI5 is actively maintained, and feedback genuinely makes it better. If you spot something wrong, unclear, or broken, please say so — corrections to lessons are prioritised. See the Contact page for how to reach out about corrections, broken examples, lesson suggestions, accessibility issues, or general feedback.