How much do I want to read more? 8/10

I like the book's approach: to distill a tiny bit of new information at a time, and 10 exercices to make it stick.
I was surprised how simple and obvious many chapters looks like to me, but it's a good reminder how far we can split knowledge we take for granted. It's also comforting to solve exercices and read chapters "easily", it build confidence.

It also gives me ideas to develop my own teaching strategies, could it be with books, videos, or person-to-person.
I didn't try online coding platform for a long time, but I guess it's a bit like this, plus some bells and wishes like graphics, animation, sound, gamification.

  1. Read a 10-minutes chapter of this book to get each concept
  2. Make the knowledge stick. Do the chapter's free interactive exercices at

Learn it faster. Remember it longer.

If you embrace this method of learning, you’ll get the hang of Python in less time than you might expect. And the knowledge will stick.
You’ll be less bored, and might even be excited. You’ll certainly be motivated.
You’ll feel confident instead of frustrated.
You’ll remember the lessons long after you close the book.

It’s a book plus almost a thousand interactive online exercises.
You’re going to learn by doing. You'll read a chapter, then practice with the exercises. That way, the knowledge gets embedded in your memory so you don't forget it. Instant feedback corrects your mistakes like a one-on-one teacher.

Cognitive research shows that reading alone doesn’t buy you much long- term retention. Even if you read a book a second or even a third time, things won’t improve much, according to research.
And forget highlighting or underlining. Marking up a book gives us the illusion that we’re engaging with the material, but studies show that it’s an exercise in self-deception. It doesn’t matter how much yellow you paint on the pages, or how many times you review the highlighted material. By the time you get to Chapter 50, you’ll have forgotten most of what you highlighted in Chapter 1.

This all changes if you read less and do more—if you read a short passage and then immediately put it into practice.
Ten minutes of reading followed by fifteen minutes of challenging practice keeps you awake and spurs you on.

If you only read, it’s easy to kid yourself that you’re learning more than you are. But when you’re challenged to produce the goods, there’s a moment of truth. You know that you know—or that you don’t

How to use this book

Study, practice, then rest.

work with this book and the online exercises in a 15-to-25- minute session, then take a break. Study a chapter for 5 to 10 minutes. Immediately go to the online link given at the end of each chapter and code for 10 to 15 minutes, practicing the lesson until you've coded everything correctly. Then take a walk.

Do the coding exercises on a physical keyboard.

Very, very few Web developers would attempt to do their work on a phone. The same thing goes for learning to code.

If you have an authority problem, try to get over it.

if you omit spaces where spaces belong, the program monitoring your work will tell you the code isn't correct, even though it might still run perfectly.
If I were to grant you as much freedom as you might like, creating the algorithms that check your work would be, for me, a project of frightening proportions.

Subscribe, temporarily, to my formatting biases.

I've had to settle on certain conventions. All of the conventions I teach are embraced by a large segment of the coding community, so you'll be in good company.

1/ print

Here's a line of code that tells Python to display the words “Hello, World!”

print("Hello, World!")

Find the interactive coding exercises for this chapter at:

2/ Variables for Strings

A variable is created this way:

name = "Mark"

Find the interactive coding exercises for this chapter at: