Learning to Code After Thirty: An Honest Timeline

Every career-change story online seems to follow the same arc: person discovers coding, falls in love, quits their job, and three months later they're a senior engineer at a startup. That wasn't my experience.

Here's what it actually looked like, month by month.

Months 1-2: The Honeymoon

Everything was exciting. I completed tutorials. I made a calculator. I made a to-do app (of course). Every small thing that worked felt like a revelation. I told everyone I knew that I was "learning to code" and genuinely believed I'd be job-ready in six months.

I was coding about forty-five minutes a day, squeezed between twelve-hour shifts and the basic requirements of being a human being.

Months 3-4: The Wall

The tutorials ran out of helpfulness. I tried to build something from scratch and realized I couldn't. The gap between following instructions and solving problems on my own felt enormous. I spent an entire weekend trying to center a div and questioning every life choice that led me to this point.

I almost quit. Not dramatically — I just stopped opening my laptop for two weeks. The shifts were exhausting, and coding had stopped feeling fun.

Months 5-7: The Grind

I came back with lower expectations and a different approach. Instead of trying to learn everything, I picked one thing — JavaScript — and committed to it. I found a study group online. Having other people to be accountable to made a bigger difference than any course.

I built a small project that actually worked: a shift-scheduling tool for my unit. It was ugly. The code was worse. But my coworkers used it, and that felt real in a way that tutorial projects never did.

Months 8-10: The Pivot

I started learning React. It broke my brain for about three weeks, then something clicked. I rebuilt my scheduling tool as a web app. It was still ugly, but it was a web app, and I could show it to people on their phones.

I also started reading other people's code. Open source projects, blog posts with code examples, anything I could find. Reading code taught me patterns that writing code alone never would have.

Months 11-14: The Job Search

This was harder than I expected. My resume was unusual — years of healthcare experience and a few personal projects. No CS degree, no bootcamp certificate. Some employers didn't know what to do with me. Others were intrigued.

I applied to forty-three positions. I got eight responses. Four interviews. Two final rounds. One offer.

The whole process took about three months. It was demoralizing, validating, exhausting, and ultimately successful — in that order.

Month 15: Day One

Walking into an office where nobody knew me as a nurse was surreal. My imposter syndrome was at an all-time high. But I sat down, opened my editor, and started reading the codebase. And somewhere between the third and fourth file, I realized something: I could follow it. I could understand what was happening. I belonged here — not because I was the best developer in the room, but because I could learn, adapt, and contribute.

The Honest Part

It took me over a year. I did it while working full-time. There were weeks where I made no progress and weeks where everything clicked. The timeline wasn't clean, and the path wasn't straight.

If you're in the middle of your own version of this, here's what I wish someone had told me: the timeline doesn't matter. The consistency does. And "slow" is just "steady" with worse marketing.