Guides
The questions that come before a course does. Each one answers in the first paragraph, shows its working, and cites what it is standing on.
- How do I know if I'm actually improving?Not by how it feels, which is the least reliable instrument you have. Improving shows up as work you could not have produced a month ago, judged against a standard written before you started. Everything else — hours logged, videos watched, a course bar at eighty percent — measures attendance rather than ability.Sources checked, not expert-reviewed
- How long does it take to learn Python?The shared core is about 30 hours across 17 skills. After that the answer splits by destination — scripting stops there, data work adds SQL and a library, web work adds a framework and HTTP. Most published figures quietly answer only the first.Sources checked, not expert-reviewed
- How long does it take to learn SQL?About 47 hours of focused work covers 26 skills, from a first SELECT to window frames and query plans. At five hours a week that is around ten weeks; at one hour a week it is closer to a year. Hours are the honest unit here. The calendar is not.Sources checked, not expert-reviewed
- How many hours a week to learn a new skill?Two to five, split across at least two sessions, is the range where most adults make steady progress. The floor matters more than the ceiling: below about two hours a week you spend most of your time recovering ground you lost since last time, so the same annual total buys far less than it should.Sources checked, not expert-reviewed
- What should I learn after Python basics?Not a framework. The four things that separate writing Python from being trusted with it are reading a traceback, handling the specific failure you expected, writing a test that fails first, and loading a real imperfect file without lying about what you skipped. Roughly seven hours, and they unlock everything else.Sources checked, not expert-reviewed
- What's the best way to learn a skill as an adult?Use the four advantages you have and stop apologising for the constraints. You arrive with related knowledge worth skipping ahead on, you have a real goal to point at, and nobody is setting your syllabus. The costs are irregular time and no external deadline, and both are schedulable problems.Sources checked, not expert-reviewed
- Why am I stuck in tutorial hell?Because following a tutorial and starting from a blank file are different skills, and only the first one gets practised. Every tutorial removes the two hardest steps — deciding what to build and deciding what to do next — so finishing ten of them leaves those two untouched. The exit is smaller work you choose yourself.Sources checked, not expert-reviewed
- Why do I forget what I learn?Because reading something is not the same as being able to retrieve it, and only retrieval builds the path back. Memory for passively studied material drops sharply within a day. Two habits reverse most of it: testing yourself instead of rereading, and spacing those tests out rather than massing them.Sources checked, not expert-reviewed