Start Here: The Honest Truth About a Career in Software

So you want to be a software developer. Excellent choice. It is one of the few careers where a teenager with a second-hand laptop and a working internet connection can, within a couple of years, be doing the exact same job as someone with a decade of experience and a fancy degree. There is no other field quite like it.

But before you get there, we need to clear out some rubbish. There is an astonishing amount of nonsense circulating about who gets to become a developer, and most of it will either scare you off or point you in the wrong direction. This series is my attempt to give you the honest version, the one I wish someone had handed me when I started.

The myths, dismantled

You need to be brilliant at maths. No. For the overwhelming majority of software jobs, you need arithmetic, a bit of logic, and the ability to reason about cause and effect. If you can follow a recipe, argue about football tactics, or plan a route across town, you have the raw material. Some specialisations lean hard on maths - graphics, machine learning, cryptography - but those are corners of the industry, not the entrance to it.

You should have started as a child. The kid who was writing games at eleven has a head start on syntax and nothing else. Careers are long. Someone who starts seriously at nineteen and works at it will fly past the child prodigy who lost interest at fourteen. Starting age is close to irrelevant; consistency is everything.

The field is oversaturated and AI is closing the door. People have been declaring software dead since roughly 1970. Meanwhile the world keeps stuffing more software into more things - your car, your fridge, your bank, your doctor. AI has changed how we write code, and I will talk about that honestly throughout this series, but it has not removed the need for people who understand systems, make good decisions, and can be trusted to build something that works. If anything it raised the value of judgement, which is the one thing you actually build over a career.

What the job actually is

Films show developers typing furiously in dark rooms as green text scrolls past. The reality is calmer and stranger. Most of the day is thinking. You read code far more than you write it. You spend a surprising amount of time figuring out what the problem even is before you touch a keyboard. You have conversations - with colleagues, with the people who will use the thing, with your past self via the mess you left in the code last month.

The actual work is a loop: understand a problem, break it into pieces small enough to hold in your head, express those pieces precisely enough that a very literal machine can execute them, then discover all the ways you were wrong and fix them. That last part - discovering you were wrong and fixing it - is not a failure state. It is the job. If you cannot stand being wrong several times a day, this will be a rough career. If you find it interesting, you have found your people.

The one trait that actually matters

I have worked with brilliant developers and mediocre ones, and the single best predictor of who thrives is not intelligence. It is a particular blend of curiosity and stubbornness. Curiosity to ask how does this actually work? and refuse the hand-wavy answer. Stubbornness to sit with a problem that has beaten you for three hours and come back for a fourth.

Everything else - languages, frameworks, tools, interview tricks - is learnable, and this series will walk you through learning it. But that itch to understand things, and the refusal to quit when they resist you, is the engine. If you have it, even a little, you can do this.

Why it is worth it

Let me be unfashionably positive for a moment. Software is one of the great creative crafts of our time. You get to build things - real, working things that other humans use - out of nothing but thought and text. The feedback loop is fast: an idea in the morning can be running by the afternoon. The pay is good, the work is often remote and flexible, and the skills transfer across nearly every industry on Earth. You can build a business with almost no capital. You can automate the boring parts of your own life for fun.

It is also genuinely hard, frequently frustrating, and occasionally humbling in a way that can sting. I am not selling you a fantasy. I am telling you that the frustration is the price of admission to something worth doing, and that the people who make it through are not the ones who found it easy. They are the ones who decided it was worth being bad at for a while.

How to use this series

The rest of these posts walk the path in roughly the order you will travel it: whether you need a degree, how to pick a first language and stop obsessing over it, how to actually teach yourself, what to build, the unglamorous tools nobody warns you about, getting unstuck, building a portfolio, landing that first role, surviving interviews, and thriving once you are in.

You do not need permission to start. You do not need to buy anything. You need a computer, an internet connection, and the willingness to be a beginner for a while.

Let us begin.