Nine months, not nine weeks
October 17, 2026 · 5 min read
Short intensive courses teach people to follow instructions. The skill employers are actually paying for is what happens when the instructions run out.
A nine-week course and a nine-month programme are usually described as the same thing at different speeds.
They are not. They produce different people, and the difference is not how much each one knows.
What a short course can and cannot do
Nine weeks is enough to teach a syntax, a framework and a workflow. A motivated person will finish with a working project and a reasonable understanding of what they built.
What nine weeks cannot do is produce someone who is reliable when the ground is unfamiliar.
The daily reality of technical work is not writing code that resembles the example. It is confronting something broken, in a system you did not build, with an error message that describes a symptom rather than a cause, and no tutorial covering this case. The skill is holding your nerve, forming a guess, testing it, being wrong, and narrowing down.
That skill is not taught in a module. It accumulates — from having been lost, repeatedly, and having found the way out enough times to believe you will again.
A compressed course cannot contain enough of those episodes, because the curriculum is full. Being stuck for two days is the most valuable thing that can happen to a learner and the first thing a tight schedule removes.
Who short courses actually work for
They work well for people who already have most of what they need.
Someone with a technical degree learning a new framework. Someone changing specialism within the same field. Someone who has been teaching themselves for a year and needs structure and a credential.
For those people, nine weeks is efficient, because the slow part was done before they arrived.
The people a short course fails are the ones with no adjacent experience to lean on — which, often, are exactly the people a funded programme exists to reach. They are given the same nine weeks, finish with the same certificate, and then discover in interviews that the certificate was the easy part.
That outcome is worse than not running the programme. The person has lost the time, and often concludes the problem is them.
What the extra months buy
Four things, none of which can be bought faster.
A full cycle of failure and recovery. Attempt, failure, diagnosis, second attempt. That cycle is the unit of learning in technical work, and it takes weeks, not days. A programme too short to contain one has not taught anybody to recover from anything.
Work on something you did not design. Every beginner’s project is built to be understood by its author. Professional work almost never is. The first encounter with somebody else’s half-documented system is disorienting and has to happen under supervision rather than in the first week of a job.
The habit of returning. Nine months of showing up on a Tuesday when you do not feel like it builds something a sprint does not. Most people who leave technical work do not leave because they could not learn it. They leave because the first hard stretch arrived and they had no evidence they could get through one.
Time for the rest of life to be absorbed. A nine-week course assumes nine clear weeks. Participants have jobs, families, illnesses and journeys that fail. A short programme treats those as attrition. A longer one has room for a bad month, which is the difference between a participant finishing and a participant disappearing.
The honest trade-off
Longer costs more per person. With a fixed budget, depth means fewer places.
That is a real choice and it should be stated rather than hidden. Ten people trained properly is a smaller number than fifty introduced to a subject, and it will always look less impressive in a report.
We think it is the right trade, for a specific reason: a half-trained person is not half-employed. The employment outcome is close to binary. You are either capable enough that an organisation will take the risk, or you are not, and most of the value sits on the far side of that threshold. Spreading a budget thinly can mean funding fifty people to arrive just short of it.
This is not an argument against short courses generally. It is an argument against using them for people who are starting from nothing, and then counting completions as if they were outcomes.
What to ask before you enrol
If you are deciding between programmes, the syllabus will tell you less than four questions will.
How long is it, and how many hours a week? Multiply them. A nine-week course at ten hours a week is ninety hours. Be clear with yourself about what ninety hours can produce.
Will I work on something I did not build? If every project starts from an empty file, you will not have met the actual job.
What happens if I fall behind? Is there a route back, or is there only the pace? The answer reveals whether the programme is designed for people with complicated lives.
What do people do afterwards — specifically? Not a placement percentage. Names of roles, names of employers, how long it took. A programme confident in its results will tell you. One that answers in percentages is managing a number.
What this means for funders
If you are paying for training, the temptation is to maximise the headcount, because headcount is what a report can show.
The harder question is whether the people you funded can now do the work. That is answerable — it requires following up six months later and accepting an uncomfortable answer — and until an organisation does it, the number of people trained is an expenditure record rather than a result.
We would rather be asked that question than asked how many attended.
Our current programme with Bluevese funds ten young people for nine months, each studying the area of tech they chose. Read about it.
