From Photographer to Dev at 36: Why Your Age Is Your Secret Weapon

Source: Dev.to

They say “you can’t teach an old dog new tricks.” For a long time, I let that saying hold me back. At 36, after an eclectic career moving from photography to graphic design and finally web design, I decided to make the real jump into coding.

Today, I’m here to tell you that it is possible—and your age might just be your biggest competitive advantage.

1. Starting from scratch… with a full backpack

I didn’t land in programming by magic. My path was progressive, but the final decision was radical: I went abroad to join an intensive bootcamp.

Critics of bootcamps are plentiful, but for me it worked. It was my gateway. Reality hit hard, though—I felt classic imposter syndrome, surrounded by much younger peers with enviable mental agility for absorbing new syntax. For five months I lived in total immersion: I woke up with code, went to bed with code, and (literally) dreamed in code.

Soon I realized something crucial: programming is not just about typing syntax.

While my peers struggled with communication, time management, or handling frustration when a bug wouldn’t resolve, I could apply the soft skills from my previous life in sales and creative work:

• Resilience – I knew a bad day didn’t define my career.
• Communication – Years in sales taught me how to explain technical problems to non‑technical people.
• Discipline – Studying far from home and outside my comfort zone requires a level of commitment that often only comes with maturity.

2. The Learning Path: Less is More

One of my biggest early mistakes was “tutorial hell” and trying to learn everything—Python, Java, React, SQL—at once. Enthusiasm is dangerous if it isn’t focused.

What really worked for me:

• Choosing a clear path – I focused on one ecosystem (JavaScript/Web) and closed the tabs for everything else.
• Consistency over intensity – I preferred one hour of focused coding every day over a ten‑hour binge on Sundays.
• Building broken things – I stopped watching passive tutorials and started breaking my own code. That is where real learning happens.

3. The Reality of Ageism (and how to filter it)

I won’t lie: the fear of ageism is real. I worried about fitting into startup cultures full of ping‑pong tables and free beer.

It is true that some “churn and burn” companies (often called body shops) push recruiters to hire people under 30. They want workers they can squeeze to generate code quickly, without caring about quality, architecture, or professional culture.

But here’s the thing: you don’t want to work there.

Serious companies value stability. A developer who has lived through other work experiences is someone who values their position, understands the business, doesn’t need micromanagement, and brings calm during crises.

4. The Seniority Advantage in the AI Era

Companies know that AI can reduce production time, but they are also discovering that implementing AI blindly leads to low‑quality code, technical debt, and failed architectures.

Knowing how to prompt AI is useful, but being critical of AI’s answers is vital. That critical thinking—seeing the big picture and detecting when a solution makes no business sense—comes with years of life experience.

Conclusion

Your age is not a bug; it’s a feature. You have context, patience, and the ability to connect dots that others miss. If you are 30, 40, or 50 and are hesitating: do it. The tech world needs more people like you.

This article was originally published on www.codesyllabus.com.