Being taught by someone who does the job, not just someone who teaches it

There is a real difference between being taught by somebody who teaches a subject and being taught by somebody who does it for a living.

Neither is better across the board, and anyone claiming otherwise is selling something. But the difference is worth understanding, because it decides which one you actually need.

What a practitioner brings

The current version. Technology moves faster than any syllabus can. A course written three years ago describes a world that has partly moved on. Somebody working in the field is using this week’s version, with this week’s problems, and knows which parts of the documentation are now wrong.

Knowing what actually matters. Every subject has topics that dominate the textbook and rarely appear in real work, and topics given half a page that turn out to be most of the job. You only learn which is which by doing it. A practitioner can tell you where to concentrate, and where a light understanding is genuinely sufficient.

The failure stories. This is the real advantage. Courses teach how things work. Practitioners have watched them not work, at inconvenient hours, with people waiting. That experience is where the useful knowledge lives, because understanding a system properly means understanding how it breaks.

When I explain why backups need testing, I am not repeating a principle. I am describing a specific occasion when a backup that reported success for eleven months turned out to contain nothing.

Context for why anything exists. Concepts taught in isolation feel arbitrary and are hard to retain. The same concept explained through the actual problem it was invented to solve tends to stick immediately.

Honesty about the industry. What entry-level work is genuinely like. Which certifications employers care about and which they ignore. What gets asked in interviews. Whether a particular path is worth pursuing. That information is not in the syllabus and careers advisers frequently do not have it.

Where teachers and academics are genuinely better

This is the part that usually gets left out, and it matters.

They know how to teach. This is a real skill, developed deliberately, and most practitioners do not have it. Knowing a subject and being able to convey it are different abilities, and the world is full of brilliant engineers who cannot explain anything.

They know the syllabus and the marking. For a student sitting the HSC, what matters is what NESA assesses and how marks are awarded. A classroom teacher knows that in detail. I do not, and I would not pretend to.

They teach fundamentals that outlast the tools. Practitioners tend toward the specific and current. Academics teach the underlying principles, which are still true in fifteen years when every product name has changed. That is genuinely valuable and easy to undervalue when you are twenty.

They have structure. A well-designed course covers things in a considered order, including the parts nobody enjoys. Practitioners teach what comes up, which can leave gaps.

The honest conclusion

For most people learning IT, the answer is both, and they do different jobs.

Do the course. Get the fundamentals, the structure and the qualification. Then get somebody who does the work to show you what it looks like in reality, and to fill in the parts a classroom structurally cannot provide.

The theory makes the practice make sense. The practice makes the theory stick.

Courses teach you what things are. Practitioners show you what happens when they go wrong. You need both, and only one of them is easy to buy.

Which to prioritise, if you can only pick one

Choose a course if: you are starting from nothing, you need a formal qualification, you are studying for an exam, or you want a broad grounding before specialising.

Choose a practitioner if: you have the theory and cannot convert it into anything practical, you are trying to get hired and getting nowhere, you need to know what actually matters, or you learn better by doing than by reading.

That second list describes a great many recent graduates, which is why so many of them spend months applying for entry-level roles without success. They are not short of knowledge. They are short of experience, and no additional course will supply it.

The reference problem

There is one more thing a practitioner can do that no course and no online tutorial can, and it is worth stating plainly.

There is an enormous amount of excellent free material online, and you should use all of it. But a video has not watched you work. It cannot tell an employer that you stuck with a problem, that you turn up, or that you can explain what you did and why.

A person who has worked alongside you can. For somebody with no employment history yet, one credible referee who can speak specifically about what they saw you build is worth more than another certificate.

That is not something you can download.

In practice

I tutor the NSW school computing subjects alongside what students are taught in class, rather than instead of it. Their teacher owns the syllabus and the marking criteria. I bring the industry side: what this looks like in a real system, why it exists, and what happens when it fails.

For people getting into IT or changing careers, the emphasis shifts to building something real, because that is the gap the qualification leaves behind.