In the rapidly evolving internet industry of today, questions and discussions like "Is 35 a turning point for programmers?", "Do programmers really...
For further actions, you may consider blocking this person and/or reporting abuse
I'm 56, sold my first piece of commercial software (a game) when I was 15 and have been building businesses ever since - based primarily on my ability to build software and solve people's problems. I've been a CTO since 2000, I still code nearly every day, my team and I work shoulder-to-shoulder to build our solutions, we operate with as little hierarchy as possible and learn from each other.
My belief is in the solution, in solving the user's problems in the best way possible and by building robust things - this is the passion I believe we need.
Over my career I've programmed in everything from Z80 assembler to TypeScript, via a host of languages and using a series of tools - you indeed have to keep learning, it's true that learning to finish projects is more important than just starting them - it's also true that you should murder your darlings and step away from your failures with your head held high. Be good at what you are good at, and keep pushing that envelope - I'm rubbish at a whole ton of things and I could talk myself into a corner with regret about it - I've learned not to do that. Our job is about change, about new challenges and new opportunities, you can't ever think you're the smartest person or that the solution you used yesterday will be 100% right tomorrow. So you've got to find what is useful for you today.
As Jon says in his comment, I love this job, I can't ever imagine not doing it in some way. There is absolutely no way I'd reject any job applicant, at any seniority level, based on their age, gender, sexuality or race - not because it's the "woke" thing to do, but because, in my experience, it's the best thing to do.
Your comment truly resonates with me. Keep up the fantastic work!
I'm 59, but more embedded sw/hw bent. I feel the same. Well said!!!
I'm 47 and have never experienced such a crisis through almost 30 years of being a professional developer (programming for 40). I love programming and always will - that's enough for me.
I'm in the same boat, just one year younger.
Great to hear that.
So cool!
Your love and dedication to programming are undoubtedly your strongest assets in overcoming challenges.
it is amazing in this age still coding if you in china
I've been programming for 48 years. No mid career crisis. Yet.
I agree with all 4 points.
I'd also doubly emphasize: software development is a social activity, as much as it also requires technical skills. It requires good social and communication skills.
It's truly inspiring to hear from someone with such a vast amount of experience and still passionate about their craft. I wholeheartedly agree with your points, especially regarding the importance of social and communication skills in software development. In an industry often stereotyped as purely technical, the significance of teamwork, collaboration, and effective communication cannot be overstated. These skills are crucial for understanding project requirements, solving problems collaboratively, and creating software that truly meets users' needs.
I am 54, also work from Z80 -> Typescript a various tech stack. 2 years ago I found myself unemployed ... again ( startup was broke ) so I take a look a next opportunity and collect a few possibilities. My final decision is going to international company to improve my really worst communication skill ( even I do not have a great English skill ) so I try push my boundaries.
It is success, now I lead a team ( I also never work in lead position ). But I keep my first interest is the coding problems. Also get a new hobby: AI image making.
find the physical glitch on image
I don't see how any of these points has anything to do with being older than 35? I have never heard about this 35+ problem in the real world. I only read internet articles about it, and I am starting to believe that this is just a topic that is grabbed out of thin air. If people love programming when they are 35, 40 or 60, and spent a lot of time on it. Then for sure they will be better than someone with less experience. Just keep programming, and don't listen to these rumors, if you keep developing your skills, you will naturally still be able to keep a job.
Individuals who dedicate themselves to honing their craft, regardless of their age, bring a depth of knowledge and perspective that can significantly benefit projects and teams. The key is to stay curious, keep up with the latest technologies, and maintain a love for problem-solving. Age, after all, is just a number, and the diversity of experience can only enrich the tech ecosystem. Let's continue to focus on skill development and passion for the craft rather than arbitrary age limits.
This is a wonderful post, thank you. I'm 37 and have been programming since 2010. In my opinion, we can pursue programming at any age, whether we're 60 or 70. What matters is our passion for it.
Experienced developers can continue with their programming while also sharing their knowledge and wisdom with the community. They can do this through writing blog posts, giving talks, and participating in podcasts. Additionally, they could shift their focus to product development. Programming is just one aspect of product creation. The process of developing a product encompasses many layers, and areas like software design can greatly benefit from the input of experienced developers.
Technology is progressing rapidly, but there's no need for developers or programmers to compete with it. We can't learn everything that emerges each day. Instead, we can focus on improving ourselves and adapting to new innovations, like AI, rather than fearing them.
I'm 67, a mechanical engineer by degree and a software engineer by practice (39+ years and counting). Technically, i've moved into software architecture. I've spent the vast majority of my career in the UI space and i wouldn't change that for anything. I'm curious about a LOT of things outside of just UIs, so there's never a shortage of new things to learn.
As a Technical Architect, i might actually be writing more code than i did as an individual contributor (at least it feels like it). I know for certain that i help more people & projects now than i ever have in the past. The UI space has been a never-ending landscape of change, which is probably one of the reasons i like it so much. There are always new things to learn and try, which is where most of my coding is focused on (quick little prototypes to try things out or solve problems).
Looking back over my career, i've had times that i struggled more. The best advice i can give is to "Never Stop Learning". The times i struggled were the times i became complacent with what i knew and didn't actively learning new things.
I have no intentions of walking away from this, even at 67. Looking forward to see how things change in the next ten years...
So cool.
I wish I could be like you when I'm 67!
The advantage of being older is that you have seen the metal hit the road. You can spot fads from miles away. You know what will deliver (and what not). By having people follow fads you got them. They become less productive so sales can come in and hook the company on a framework (that is overpriced and makes that company loose their autonomy). When you are in a company where management fell for a fad, you need to move on or you loose yourself in this mid-career crisis. It will happen every 7-10 years. Systems are now breaking down left and tight. The same happened before the cloud came. It is now breaking down to sell the world on AI. Every cycle is more consolidating into less hands. Now that you know this, you have time to (re)position yourself.
It hit me exactly at 35-36 yo.
I was so bored by same kind of problems to solve and same kind of clients that did not understood that getting an ecommerce website up and running is not enough to have a successful business online.
I took a step back and open a motorcycle repair shop. I felt that doing something with my hands, something in the physical world will be more rewarding and I was right, it felt amazing. Of course I've used my skills to integrate & automate many of the processes in the repair shop and I love it. It took me 3 years to switch back to full SWE.
Fast forward, I'm 47 now, learning new stuff every day and loving every minute of writing code, explore new technologies and share that within the team.
I disagree with the direct cause-and-effect relationship between the issues you mention and age. There are people who at 20 years old are more settled than many at 70 years old.
I agree with your opinion
Thank you for sharing