LEARNING · FROM BOOKMARKS TO A FIRST ATTEMPT
Make a self-study plan you can put to use.
Choose something small to make or do, try a resource before committing to it, and decide how you will check your work.
You want to learn a skill. You have saved a course, a few videos and a long reading list. Each looks useful, but opening the folder still leaves you with the same decision: where do I start?
Before making a study schedule, choose a task that will help you judge those resources. A first plan can be small enough to fit in a few notes: what you want to do, what you need to start, which resource you will try, and how you will check the result.
If you already have a course with a syllabus and need to return to it, use the course-restart guide. This guide is for the earlier decision, when you are choosing your own path.
Turn a subject into a small task.
“Learn web development” leaves almost every choice open. “Make a simple page about a place I like” gives you something to work toward. The same move works for other subjects: choose one conversation you want to hold, one kind of problem you want to solve, or one passage you want to play. Then decide what a useful first attempt would include.
Fictional worked example · A first learning task, not a complete curriculum
Sam's first page
Sam wants to make a webpage about a favourite park. The first version will be a file opened on Sam's own computer, containing a heading, a short paragraph and a descriptive link to the park's official information page.
Colours, pictures, animation and publishing can wait. Sam wants to understand this small piece before choosing the next one.
Starting point: Sam can create and find files and use a browser, but has never written HTML. A code editor is already installed. Those details matter when choosing a beginner resource.
Keep the first task narrow enough to inspect. If you cannot say what you would look at or listen for, make the task more specific. For skills where you cannot judge correctness yourself, decide who could give useful feedback before treating a finished attempt as success.
Try a resource before committing to it.
Choose a promising starting resource and inspect one relevant section. You do not need to rank every book or course available. Use these four questions to find out whether this one can help with the task in front of you.
- Does it teach the thing I want to do? Find the lesson, chapter or example that matches your small task. A broad title alone is not enough.
- Can I start with what I already know and have? Check prerequisites, tools, access and any cost. Name a missing prerequisite instead of repeatedly struggling with an unexplained step.
- Can I try a small piece now? Attempt a step, exercise or example. Notice whether you can follow the explanation well enough to act on it.
- How will I check what I tried? Look for an answer with reasoning, a result you can inspect, or a person who can give informed feedback. Decide what the resource cannot check for you.
A resource can be credible and still be wrong for your starting point. Keep the decision tied to what happened when you used it.
What Sam learns from a short trial
Sam opens MDN's Your first website module. It lists basic computer and file skills, a code editor and browsers as prerequisites, with an environment-setup route for anyone who needs it. Sam then finds the Creating the content tutorial, which covers the heading, paragraph and link needed for this task.
- Observed: the first step is usable.
- Sam follows the document setup and heading example, saves the file, and opens it in a browser. The heading appears. Decision: keep this tutorial as the main resource for the first page.
- Observed: there is much more material than this task needs.
- The module also leads to styling, interactivity and publishing. Decision: defer those sections. They are useful later; they do not need to become today's assignment.
- Observed: a specific detail may need a second look.
- Sam keeps the tutorial's link section easy to find. Decision: use it as a reference when checking the page, rather than starting a second course.
If Sam could not save and locate the file, the next action would be environment setup. If the explanation remained unclear after an attempt, Sam could try another explanation of that same small task. Neither problem requires abandoning the whole learning goal.
Decide how to check the result.
Write the checks before calling the task finished. For Sam's page, the checks are concrete:
- The saved page opens and contains the intended heading and paragraph.
- The link text tells a reader where it leads. Activating it opens the intended official park page.
- Sam can point to the part of the HTML that sets the link destination and explain what it does. Looking up the syntax is allowed; the note should say when help was used.
These checks cover a small task. They do not establish that Sam can build an accessible, polished website, publish one, or solve every HTML problem.
Fictional attempt and correction
The page opens. The link does not go anywhere.
Sam's heading and paragraph appear, but the link has no href attribute, so it has no navigable destination. The note reads: Page opens; link destination missing. Used the tutorial to find the missing part.
Sam adds the intended address, saves the file, reloads it and tries the link again. It now opens the correct park page. The correction goes in the note too.
Next task: make a second page about a different place without following the tutorial line by line. Look up details when needed and record the help used. Check the new link's destination again.
The first attempt was enough to reveal a useful next step. Sam can keep the resource and work on using the idea in a new page. A missing destination does not, by itself, mean the whole tutorial is unsuitable.
For your own skill, keep the attempt and the feedback together: a recording with a teacher's comment, a solved problem beside the worked answer, or a draft with a specific revision. A study session tells you that you put in time. The work and its check tell you what to try next.
Keep a short plan you can change.
Here is Sam's plan after the first trial. Copy the headings into your own notes and replace the details.
- Small task
- A local page about a favourite park, with a heading, paragraph and working descriptive link.
- Starting requirements
- File and browser skills; editor ready. Return to setup guidance if saving or locating the file becomes a blocker.
- Main resource
- MDN's Creating the content tutorial. Focus on the parts needed for this page.
- How I will check
- Open the saved page, inspect its content, test the destination, and explain the link with any help noted.
- What I found
- Heading and paragraph worked. Link needed a destination; corrected using the tutorial and checked again.
- Next attempt
- A page about a different place. Use references as needed, then compare what required help.
- When I will reconsider the resource
- If a prerequisite is missing, address it first. If I still cannot follow a relevant explanation after trying it, compare another explanation for the same task.
Now choose a time for that next attempt. Allow for setup and checking as well as reading or watching. You can use the goal action-plan guide if you want to turn it into a regular week.
You do not need to plan the entire subject today. Make the next choice from what the last attempt showed you.
Sources and scope
The University of Waterloo's Self-Directed Learning: A Four-Step Process discusses goals, resources, feedback and evaluation in a university setting. It is relevant educational guidance, not a study of this plan.
MDN's beginner module and HTML tutorial support the resource choice and technical details in the example. Sam, the park-page task and the attempt record are fictional. The example shows one starting decision, not a complete web-development curriculum or a promised learning result.
Sources checked November 1, 2026.