Developer · Lecturer · Writer
About Len Johnson
I lecture in computing. I still take client work.
The two roles do not usually overlap. The gap between having development skills and getting paid for them is where my teaching, client work and writing meet.
In education
Fourteen years in further and higher education.
Currently teaching Level 5 Web Application Development and HND Computing.
In development
Building and selling web work since 2000.
Websites, applications and digital products built for real users, clients and businesses.
The distinction that matters
I was doing the work before I had the credential.
I built and sold web work for years without the degree that job adverts often demand. I have one now because I needed it to teach the subject, not because I needed it to do the work.
That distinction is a recurring theme in my writing. Qualifications matter, but they are not the same thing as professional capability. Code matters, but code alone is not the whole job.
The difficult part is not always learning to build. It is crossing the gap between being able to build and being trusted to deliver.
What I watch happen
Capable developers meet a closed front door.
Students leave courses and bootcamps able to build useful things, then struggle to get close enough for anyone to notice.
An entry-level vacancy can attract hundreds of applications. Employers need a manageable shortlist, so simple filters reduce the pile before anyone has formed a serious view about most candidates’ code.
That is not proof that those developers are not good enough. It is evidence that applying through the front door is a weak strategy when everybody is standing in the same queue.
Inside the application pile
Hundreds of applicants. Fast filters. Very little attention per person. Your evidence may never be examined.
The useful move is to create situations in which somebody is looking closely at exactly one person.
Outside the pile
A referral. A local business with a problem. A freelancer who needs delivery help. A real user who needs something built.
What I think counts
Delivery changes the quality of the evidence.
A qualification demonstrates learning. A portfolio demonstrates technical ability. Live users, client outcomes, references and revenue demonstrate the thing neither can: delivery.
Qualifications
Evidence of learning
They show that you completed a recognised programme and met its academic requirements.
Portfolios
Evidence of ability
They show what you can design and build when you control the problem, scope and conditions.
Real work
Evidence of delivery
It shows that you can understand somebody else’s problem, make decisions, finish the work and answer for the result.
Freelance work, small-business projects, productised services, independent products, open source and adjacent technical roles can all produce that evidence. None requires an employer’s permission first.
On AI
Leverage, not substitute.
AI has made the distinction between production and professional judgement sharper, not safer.
Routine production is becoming cheaper. Requirements analysis, evaluation, integration, judgement and accountability are becoming more important.
Use AI to produce. Do not use it to understand on your behalf. If you cannot explain it, debug it and answer for it when it breaks, you have not built anything.
What I write about
The commercial layer surrounding the code.
Scoping, pricing, boundaries and evidence: what happens between building something and being paid for it.
Learn to code inside a job and you absorb much of this by accident. You sit near people who have quoted badly and recovered. You hear how scope conversations go. You watch somebody turn an uncertain request into a deliverable.
Learn outside a job and much of that experience never reaches you, even though it is the layer that determines whether technical skill becomes useful paid work.
It is not secret knowledge. It simply is not written down often enough. Brief to Invoice is my attempt to write it down.
The free book
Fourteen chapters explaining five realistic routes towards paid work, including the money, timelines, risks and honest downsides.
The newsletter
Every fortnight, one realistic client brief taken apart: what it means, what to ask, what to include and the arithmetic behind the price.
What this is not
This is not a pitch for my services.
I am not touting for clients and I am not looking for a role.
I do still take the occasional client job, deliberately. The details worth teaching and writing about come from continuing to do the work, not simply from having done it once.
If you want to talk about computing education, junior developer employability, AI-assisted development or authentic assessment, those are conversations I am glad to have.
Start with the book
Nobody’s hiring juniors. Get paid anyway.
Fourteen chapters. Five routes to earning from your development skills. Free to read, with no course attached.