How I Build Expertise Without a Linear Career Path

In 2022, I wrote that several years at university were not the only route to competence. I still believe that, but the original title went too far.

Independent learning does not replace the qualifications required in medicine, law, regulated work, or roles where an error can directly harm someone. It can still build serious expertise in many technical and creative fields.

I Start With a Problem, Not a Label

I do not begin by trying to become an “expert.” I choose a problem I want to know how to solve.

In software engineering, that may mean:

• designing authentication that users understand;
• diagnosing a slow database query;
• releasing an application with a rollback path;
• making an interface usable with a keyboard;
• documenting an architecture decision.

The problem gives the work a boundary. It also gives me a way to check whether I learned anything.

My Learning Loop

I use six steps:

1. read several serious sources;
2. reproduce a minimal example;
3. apply the idea to a real project;
4. document what worked and what failed;
5. request specific criticism;
6. revise the project using that criticism.

Reading without applying creates an impression of mastery. Building without reading can repeat mistakes that are already understood. I need both.

I Keep Evidence of Progress

A certificate shows that someone completed a defined path. With independent learning, I need to produce my own evidence: code, tests, documented decisions, articles, presentations, or reviewed contributions.

I do not only count completed projects. I ask whether another person can understand the work, check it, and identify an error.

Useful evidence also states its limits. A prototype does not prove that a system can run in production. Following one tutorial does not prove that I can diagnose a different failure.

I Explain to Test My Understanding

My original article emphasized teaching. That still matters. Explaining an idea forces me to clarify the words, steps, and assumptions.

I can write a note, help a colleague, present a decision, or answer a technical question. I do not need to sell a course. The purpose is to find the point where my explanation becomes vague.

When someone finds an error, I correct the article or code. That correction is part of the learning.

I Know When I Need Formal Structure

A structured path is useful when I lack foundations, critical feedback, access to equipment, or professional recognition. A university, recognised programme, mentor, or experienced team can provide that structure.

I do not treat formal education and independent learning as opposing camps. I choose the structure that fits the risk, profession, and expected level of evidence.

The path can be non-linear. The standard of proof should remain visible.