Learning to Code on a Holiday Flight: Skip the Videos, Bring Something That Runs Code
Thanksgiving week and the second half of December put a lot of people in a seat for three to six hours, often with nothing to do. Many of them have the same plan: this is the flight where I finally start learning to code.
Most of them prepare the same way, too. They download a pile of tutorial videos the night before, then land having watched a third of a course and remembering almost none of it.
I think that plan is backwards. The best use of a long flight isn't taking in information. It's practice: typing code, running it, and fixing it when it breaks. A plane is a good place for that, as long as you bring the right tools.
Why downloaded videos are the wrong bet
Watching someone code feels like learning, but mostly it isn't. You follow along, nod, and feel like you understand, until you face a blank screen and can't write the first line.
On a plane, it gets worse:
- No room for two screens. Coding videos assume you have an editor open next to them. On a phone, you're stuck switching between apps. On an iPad, you're squeezing split view onto a tray table.
- Nowhere to check your work. When your version of the example doesn't match the video, you have no way to find out why.
- Battery drain. Hours of video playback drain a battery faster than reading and typing do, and not every seat has a working outlet.
- Passive time is easy to give up. Once the in-flight movie starts looking better than the lecture, the session is over.
Typing and running code solves every one of these problems. You stay active, you get instant feedback, and the device only has to do one thing.
What you can and cannot do offline
Be honest with yourself about the limits before you board. They're real, but they matter less than you'd expect.
What works well with no internet
- Writing and running short programs in a single file
- Working through exercises right after you read about the concept
- Reading error messages and debugging your own mistakes
- Writing SQL queries against a small local table
- Rewriting a program you already finished, this time without looking
What does not work
- Installing packages or libraries
- Calling web APIs or fetching data from anywhere
- Searching the web for an error message
- Cloning a repository or setting up a large project with dependencies
For a beginner, that second list matters less than it looks. You don't need packages to learn loops, functions, conditionals, lists, or classes.
Cutting out the setup is actually a win. Setup is where many beginners lose an entire evening without writing a single line of code.
How to plan a 3 to 6 hour coding session
Treat the flight like a study block with a beginning, a middle, and an end. Here's a plan for a flight of roughly four hours.
The night before
- Choose one language and one goal, such as "understand loops and solve every challenge that uses them."
- Put your phone or iPad in airplane mode at home and confirm that everything you plan to use still works.
- Fully charge your device, plus a battery pack if you have one.
On the plane
- Boarding and climb (20 minutes): Read lesson text only. Hold off on writing code, since the tray table isn't down yet.
- Block one (60 minutes): Learn one new concept and do every exercise for it. Run each one, even the ones that seem obvious.
- Meal service: Put the device away. Get up and stretch if you can.
- Block two (60 minutes): Go back to challenges you already solved, reset them to the starter code, and solve them again without the hint or the lesson. This is where the learning actually sticks.
- Block three (45 minutes): Break your own solution to a challenge on purpose. Delete a colon, misspell a variable, or pass in the wrong type. Read each error and fix it.
- Descent (15 minutes): Write down everything that confused you. That list is what you'll look up once you're back online.
On a three-hour flight, skip block three. On a six-hour flight, add a second round of re-solving with slightly harder challenges.
Save the projects for when you land
The flight is for practice. Your first real project comes after, at home on a laptop, using what you drilled on the plane. A few holiday ideas to start with:
- A tip and bill splitter for the family dinner out
- A gift budget tracker that warns you when you overspend
- A time zone converter so you know what time it is back home
- A SQL table of who's coming to Thanksgiving and what each guest can't eat
Pick one language, not three
A flight is too short to sample a little of everything. Choose one language and stick with it for the whole trip.
- Python if you've never coded before. Its syntax stays out of your way.
- Swift if you want to build iOS apps someday.
- JavaScript if you're interested in the web.
- SQL if you work with spreadsheets or data at your job.
- Java or Kotlin if Android development appeals to you.
- C# if you're curious about game development.
Where Codewise fits
We built Codewise for exactly this situation. It has 280+ short challenges across Python, Swift, JavaScript, Java, Kotlin, C#, and SQL that you type and run on your iPhone or iPad. Everything works fully offline, because the interpreters are built into the app, so you can press run and see the result at thirty thousand feet with the Wi-Fi off.
There's no account to create, and it's a one-time purchase, so there's no subscription and no sign-in that has to reach a server before you can study. Download it before your trip, test it once in airplane mode, and it'll be ready whenever you have time to fill.
The missing internet is the best part
At home, every error message turns into a search, and every search turns into twenty minutes of reading other people's answers. On a plane, you have to read the error yourself and work out what it means.
That's the core skill in programming, and holiday travel gives you hours to practice it without interruption. Land with a set of challenges you can solve from memory and a short list of questions, and you'll have gotten more out of the flight than any video course could have given you.