I started learning to code at 40. I’m 50 now, working as a Senior Software Engineer at Dell Technologies.
That sentence is the part people find encouraging, so I want to be careful with it. It’s true, it took ten years, and the ten years is the part the ads leave out.
The Gap Nobody Prices In
The tutorial platforms are genuinely good at what they do. You follow along, you type the code, it works, and you feel like you’re learning. Then you close the tutorial, open an empty file, and discover you can’t start.
That gap — between following along and building something unassisted — is where most people quit. It isn’t a knowledge gap you can fill by watching more. The only thing that closes it is producing bad work on your own, repeatedly, which is far less pleasant than watching someone competent do it correctly.
I don’t think the platforms are dishonest about this so much as structurally unable to sell it. “Watch this and you’ll feel capable” converts better than “produce forty broken things, and the forty-first will work.”
The Constraint Was Never Aptitude
Here’s what actually made it hard, and it’s the thing nobody frames correctly: I wasn’t short on ability. I was short on hours.
A full-time job. Two kids. The window that’s genuinely mine starts after everyone else is asleep, it isn’t long, and I was already tired when it opened. An hour in that state isn’t the same as an hour at twenty-two with a whole evening ahead of you. It’s enough to reload where you left off and make a little progress, and then it’s gone.
Ten years is what that adds up to. Not because the material takes ten years, but because that’s how long it takes at the pace a life like that allows. If you’re starting in similar conditions, plan for the pace you actually have rather than the one in the course description. The people who quit mostly aren’t the ones who couldn’t learn it — they’re the ones who measured themselves against a schedule that assumed no job and no dependents.
What Real Estate Actually Gave Me
On paper, brokerage looks like a dead loss when you move into engineering. It wasn’t, though not in the way career-change posts usually claim.
It wasn’t grit or hustle. It was the habit of explaining complicated things to people who have every right not to understand them, and doing it without condescension, because their money is on the line and their confusion is reasonable. Contracts are dense and the consequences are real, and you learn to go slowly and check that you’re actually being understood.
That’s most of what technical communication is. Explaining a bug to someone who wasn’t in the code with you. Writing up an incident for people who need the shape of it, not the stack trace. Telling a stakeholder something true they don’t want to hear. I arrived with that already built, and it has mattered more than a head start on syntax would have.
Imposter Syndrome Doesn’t Resolve
Ten years in, I still get days where I feel like I’m getting away with something. I expected that to fade with competence. It didn’t.
What changed is that I stopped treating it as evidence. Early on, sitting in rooms with people who had CS degrees, I took the feeling as information — proof I didn’t belong. It isn’t information. It shows up regardless of whether you’re doing well, and the people with the degrees have it too. You don’t get rid of it. You get better at continuing while it’s there.
What I’d Actually Do Differently
Ask sooner. I lost real time to the belief that figuring it out alone was the honest way to learn. It isn’t more honest, it’s just slower, and the people I avoided asking would mostly have been glad to help.
Build ugly things earlier. Hours of tutorials feel like progress and largely aren’t. The learning starts when you make something yourself that barely works.
Write it down from day one. The problem you just solved, the concept that finally landed, the explanation that made it click — you will need all of it again, and you will not remember. I started keeping notes far too late and I still regret it.
The Honest Version of the Encouragement
If you’re considering this at 40, or 45, or 50: it’s genuinely possible. I’m the evidence, and I’m not exceptional.
It will also take longer than you want, some stretches will feel like nothing is moving, and you’ll consider quitting more than once. Those aren’t signs you got it wrong. That’s what the process looks like from the inside for someone doing it around the edges of an existing life.
The bootcamp ads compress it into twelve weeks. Mine took ten years. Both are real numbers, and only one of them was available to me.
Thinking about making the switch? Find me on LinkedIn.
