How many hours does learning a tech craft really take?

"Become a developer in 30 days." That sentence says nothing until you know how many hours per day it assumes. Thirty days at two hours an evening is not the same course as thirty days full-time — yet both get sold with the same headline.

That is why every track in the CoursTech catalogue states a real hour count instead of a duration in weeks: 30 hours for an applied-AI module, 85 hours for mobile development, 120 hours for full-stack web development. That number does not move, whatever pace you choose. It is the actual amount of work — lessons, graded exercises, final project included — needed to go from the start to certification.

The number of weeks, on the other hand, is derived from the hours you have, not the other way around. At 4 hours a week, a 120-hour track takes about 30 weeks. At double that pace, 15 weeks. This is not a marketing trick: it is the same arithmetic that applies to any learning, whether you make it visible or hide it behind a promise in days.

The classic trap is copying someone else's pace without knowing their real hours. Someone who "finished in six weeks" may have put in 20 hours a week; reproducing their calendar with 4 available hours only leads to failure and discouragement, for a problem that did not exist in the first place.

In practice, before choosing a track, ask yourself one question: how many hours a week can I really sustain over the whole duration, not just the first week when motivation is high? That answer, crossed with the stated hour count, gives a realistic calendar — and it is exactly what the 8-question orientation module computes.