Learning to code: tutor or online course?
There is more free material on programming than any person could finish, and most people who want to learn to code still do not. The bottleneck is almost never information.
What each one is actually good at
A course is good at structure, breadth, and the first two weeks. It gives you a syllabus, in order, cheaply, and you can pause it. If you have never written a line of code, start with a course, not a tutor.
A tutor is good at the things courses cannot do: getting you unstuck in ten minutes instead of two days, reading *your* code, telling you what to build next, and being an appointment you cannot silently abandon. Accountability is an underrated feature.
The stuck-alone problem is the real reason people stop. A bug that takes a beginner four hours takes a tutor four minutes to explain, and the explanation is the part you keep.
The pattern that works
1. Course for the syllabus. Follow one, in order, and do not switch. 2. Build something small of your own as early as you can bear to — the course project is not yours, so it teaches you less. 3. A tutor every week or two for: reading your code, unblocking, and deciding what to build next. One lesson a fortnight is often enough alongside a course. 4. Push the work somewhere public, so you have a record and something to show.
How to use the hour well
Bring the code. A programming lesson where the tutor lectures is a worse course. A good hour looks like:
- ten minutes on the thing you are stuck on, with you driving the keyboard;
- twenty minutes reading your own code together — naming, structure, the function that is
- ten minutes on the concept behind the mistake you keep making;
- the last ten minutes deciding what to build before next time.
The single best question to bring is "why does this work?" about code that already works. That is where the level jumps.
When a tutor is worth more than the money
- You have been "learning to code" for over a year without finishing anything.
- You are preparing for interviews. Technical interviews are a performance skill and
- You have a real project with a deadline and you need someone who has shipped one.
- You are switching languages and want the map rather than the tour.
- You are twelve. Children learn to program much faster with someone watching.
Where to look
Programming tutors list the languages they teach and what they work on — code review, interview preparation, project help. Lessons here run from $5 to $26 an hour, so a fortnightly lesson alongside a free course is an affordable way to stop being stuck alone. If you would rather describe the project than browse, you can post what you need and let matching tutors reply with a plan.
Try it with one tutor first
The $5 Trial Pass buys 25-minute trials with up to four tutors, so you can meet several before you commit to a course of lessons.
See programming tutorsQuestions people ask
Is a programming tutor worth it if courses are free?
Courses are better at the syllabus; tutors are better at the two things that stop people — being stuck alone and having nobody to answer to. A fortnightly lesson alongside a free course is a common, affordable pattern.
What should I bring to a programming lesson?
Your own code and the thing you are stuck on. The most useful lessons are spent reading what you wrote, with you at the keyboard, and deciding what to build next.
Can a tutor prepare me for technical interviews?
Yes, and it is one of the clearest cases for a tutor: technical interviews are a performance skill that needs rehearsal with someone who interrupts and follows up.
