Choose your starting point and a realistic study plan

What you will learn

• Choose a starting lesson using evidence rather than a job title.
• Turn your available time into a realistic weekly plan.
• Record a small result, a mistake, and a next action.

Theory: a roadmap is a guide

A roadmap is an ordered list of skills. It is not a list of things you must finish before applying for a job. You can already work in Laravel and still need practice with HTTP, SQL, or tests. That is normal. Start where you can explain and complete the exercise with some effort.

Reading, practice, and quiz results tell you different things. Reading shows that you studied an explanation. Practice shows that you tried the work. A quiz checks a limited set of ideas. None of these alone proves that you can build a production system. Keep examples of working code and explain your choices.

On this site, public lessons are ready for reading. Planned tracks are outlines. A verified account can keep private notes, bookmarks, progress, and quiz attempts. Mark practice only after you try it. A lesson with a scored quiz also needs a pass for its current version. A later revision keeps your earlier history and shows that there is an update to review.

Find a useful starting point

Use these four small checks. This is a manual starting-point exercise, not an automatic diagnostic or a hiring test.

Give each check a label: can explain, can do with help, or need to learn. Do not turn these labels into a fake skill percentage. Keep one example that supports your label. Revisit it after a week.

Worked example: a small study budget

Required: PHP 8.4 or a compatible newer runtime. No Laravel, database, Python, or paid service is needed for this example. Use /getting-started to check your command. Save this file as study_baseline.php in a practice folder:

<?php

declare(strict_types=1);

$dailyMinutes = [30, 30, 0, 30, 30, 60, 0];
$weeklyMinutes = array_sum($dailyMinutes);
$sessions = 0;

foreach ($dailyMinutes as $minutes) {
    if ($minutes > 0) {
        $sessions++;
    }
}

echo 'Planned minutes: '.$weeklyMinutes.PHP_EOL;
echo 'Study sessions: '.$sessions.PHP_EOL;
echo 'Next evidence: explain one request and run one example.'.PHP_EOL;

From that folder, run php study_baseline.php. This command is the same in Windows PowerShell, Windows Command Prompt, and Ubuntu Bash if PHP is on your PATH. If it is not found, select your installed PHP executable using the setup guide. Laragon and XAMPP are optional tools.

Expected output:

Planned minutes: 180
Study sessions: 5
Next evidence: explain one request and run one example.

The seven numbers represent seven days. Zero is a rest day. array_sum adds the numbers. The loop counts days with some study time. You will learn this PHP syntax in the foundations lessons. Here, use the result to make a plan you can actually follow. Planned time is not completed time.

Guided practice

1. Run the unchanged example and compare all three output lines.
2. Change the first 30 to 15. Expect 165 minutes and five sessions.
3. Change all seven values to zero. Expect zero minutes and zero sessions.
4. Restore a realistic plan. Use whole numbers from zero upward; negative time has no meaning here. The small example assumes valid input and does not validate a form.
5. Write one goal that fits a session: “Run the request example and explain the response.” Avoid “Learn all backend development.”

Independent exercise

Choose a weekly plan with no more than 210 minutes. Reserve one session for review and one short English explanation after each coding session. Write your four starting-point labels with evidence. Save a private note in the site if you have a verified account, or use a local text file.

Success means you have a realistic budget, one concrete next lesson, and evidence for each starting label. There is no single correct schedule. If work or family changes your week, reduce the plan and choose the next small action. Do not erase earlier learning because you missed a day.

Common mistakes

• Counting planned minutes as completed work: record the result of the exercise separately.
• Opening every track at once: choose one main sequence and keep a small English habit.
• Copying an answer without running it: change an input and predict the new output.
• Waiting until you know everything: practise with a small problem and review your mistakes.

Self-check — not graded

1. Does reading a lesson prove production-level skill?
2. What should you keep when a new lesson version appears?
3. What is useful evidence for a starting-point label?

Interview practice

“How do you learn a technology you have not used?” Describe a small goal, official documentation, an example, a test, and a mistake you corrected. Explain what you still need to learn.

English practice and glossary

• Roadmap: an ordered guide to skills.
• Evidence: something you can show to support a claim.
• Prerequisite: knowledge needed before another lesson.
• Review: checking something you learned earlier.
• Budget: the time or money you can use.

Write: “I can __ with help. I checked __. My next step is __.” Say it aloud slowly. Clear meaning matters more than a complicated sentence.

Recap and next step

Choose a starting point, run something small, and keep evidence. Next, trace how a request reaches a Laravel route. Source links and the review date appear in the lesson references.