How to practice coding when you only have an hour
A one-hour coding practice you can repeat on a weeknight: recall, one exercise you write, a short note, and a start line for tomorrow.
You opened a tutorial, and the hour you meant to spend practicing is gone. What do you actually do with sixty minutes?
Short answer: one exercise, written by you, with a stop time. The tutorial stays closed until you are stuck on that exercise.
By the end of this post you will have a repeatable hour: a short recall, one small change in a real exercise, and a note for tomorrow. It is not a 30-day plan. If you want that kind of map, how to learn to code in 2026 and the Python roadmap already cover it. This post is the evening in between.
Why the hour disappears
A tutorial feels like practice because your hands are moving. You are copying someone else's path, so the hour ends with a finished demo and a fuzzy memory. The next evening you open another tab, because nothing in the last hour asked you to decide. That is tutorial hell in miniature. The longer guide is how to escape tutorial hell. The fix for a single hour is smaller. You need a task that fails if you only watch.
An hour is also short enough to waste on setup. Installing a tool, picking a project, and reading three intros can consume the whole block. Everything on Start.dev runs in the browser, so a practice hour does not have to start with an install. Pick the exercise before you sit down, or the choosing will eat the time.
A repeatable hour
Use the same shape often enough that you do not renegotiate it. Four parts is enough. The times are a guide, not a law.
- Ten minutes to recall, without the lesson open. Write what you think the last concept does, in two or three sentences, or type the smallest example you can remember. If you cannot remember it, that is the note for later. Do not refill the ten minutes with a video.
- Thirty-five minutes on one exercise. Change one thing: a function, a condition, a component, a query. Run it. Read the failure. Change it again. The goal is a working change you made, not a new chapter.
- Ten minutes to write what broke. One paragraph is enough: what you tried, what the error said, and what you would try next. Make it the next edit, not a diary. "Study exceptions" is too vague. "Catch
ValueErrorand ask again" is something you can start on tomorrow without rereading anything. - Five minutes to name tomorrow's start. One sentence, such as "finish the ticket count when the input is blank." If you're not sure what comes next, ask the Study Advisor "What should I study next?" It answers from what you've actually done. Then close the tab. The next hour should not begin with a search.
If you only have forty minutes, keep the exercise and the note, and skip the recall. If you have ninety, do not add a second tutorial. Add a second attempt at the same exercise.
One hour, on a real exercise
Here is the shape on a Python evening, after you already know what a loop is. The exercise is Re Asking Until Valid (opens in a new tab), picked the night before.
In the first ten minutes you close the lesson and write, from memory, what should happen when someone types a word instead of a number. If you write "it crashes," that is a useful wrong answer. You now know the gap.
The next thirty-five minutes are the loop. You ask for a ticket count. You reject a blank. You reject a word. You keep the first whole number that is at least 1. When int() raises ValueError, you do not open a second tutorial about exceptions. You read that one message, catch it, and ask again. If you finish early, add the rule that 0 is not an order. That constraint is still the same exercise. (If you want the whole pattern written out afterwards, our post on Python input() and validation walks through it.)
The ten-minute note can be this short: "Blank input skipped the int() call. A word still raised ValueError until I caught it. Tomorrow, reject numbers below 1 before I store the count." The last five minutes are that tomorrow line, written where you will see it. Then you stop, even if the function is not pretty.
A JavaScript evening is the same shape on a different exercise. Open Project Fizzbuzz (opens in a new tab). Recall from memory what % returns. Add one rule of your own, such as printing "Bazz" for multiples of 7, and run it. Write down what printed in the wrong place, and name the next edit. Do not switch languages in the same hour to make it feel productive.
What counts as the exercise
The exercise has to be something you can fail. A video chapter does not count. A blog post, including this one, does not count. A lesson that asks you to write code and checks the result does count.
The best fit for a one-hour block is a challenge set. Each one is six focused problems on one topic, labeled beginner to advanced, and takes roughly an hour. Pick the set for the skill that feels shaky:
- Python: Python Conditionals, Python Loops, Python Lists, Python Functions
- JavaScript: Conditionals in JavaScript, JavaScript Loops, JavaScript Arrays, JavaScript Functions
A coding lesson works too. In Python, Hello Python (opens in a new tab) is a small start, and Re Asking Until Valid (opens in a new tab) is a better one once loops feel familiar. In JavaScript, JavaScript Basics (opens in a new tab) is built from the same kind of short coding lessons. Pick one language for the month. Switching stacks every evening is how the hour stays shallow. If you're learning React, the same rule applies, and how to learn React without getting lost gives you the order.
A good exercise is slightly too hard. If you finish in five minutes, add one constraint, such as rejecting a blank answer or rendering a second item. If you are still stuck at minute twenty, that is the session working. Write down the exact error, then ask Stuart about it. He can see your code, tests and output, so he can explain that one error without handing you a whole new tutorial. Take the hint, then make the next attempt yourself.
When the hour goes wrong
- Opening the tutorial first. You will follow it to the end and call that practice. Start from memory, even a wrong memory.
- Choosing the project during the hour. Pick the lesson or challenge set the night before. The hour is for the attempt.
- Collecting three topics. One function, one bug, one note. A second topic can wait until tomorrow's five-minute line.
- Quitting because the test failed. A failing check is the practice. The note is where that failure becomes useful.
Realistic expectations
One hour will not make a concept feel finished. It will make tomorrow's start obvious, which is the part people skip. Spreading practice across several short sessions tends to stick better than cramming it into one long day, and each of these evenings ends with a decision you made. Some evenings will feel wasted. That happens when the exercise was too big, or when you were tired. Shrink the exercise next time. Do not replace the hour with a longer video to make up for it.
There is no honest promise that this routine produces a job. It produces reps. Getting hired is a different question, which our guide to landing your first developer job without a CS degree covers.
Frequently asked questions
Is one hour a day enough to learn to code?
It's enough to make steady progress, as long as the hour is spent writing code rather than watching it. Regular short sessions add up, and they're easier to keep than the occasional long weekend.
What should I practice when I'm stuck?
Stay on the same exercise. Write down the exact error, ask about that one error, then make your next attempt. Switching to a new topic feels like progress, but it leaves the gap where it was.
Should I practice with projects or exercises?
In a single hour, exercises. A project needs choosing, setting up and planning, which can eat the whole block. Short exercises and challenge sets let you spend the hour on the code itself. Projects are better for longer sessions once the basics feel solid.
How do I choose what to practice next?
Use the note from the end of your last session. If it doesn't point anywhere, ask the Study Advisor what to study next, or pick the challenge set for the topic that felt shakiest.
Where to go next
Pick tomorrow's exercise before you close this tab. If you do not have a course open yet, JavaScript Basics (opens in a new tab) and Python for Beginners (opens in a new tab) are both built as short lessons you can finish inside an hour. Start with the one you already opened last week, not a third language.
