4 ms·
I'm 27. That's too late?
by rewgs 9y ago
I'm 27. That's too late?
- philippejara 9y agotoo late for what? if you enjoy programing just keep programing.
- spraak 9y agoNo, I don't think so. I was just applying the number from my own experience when I thought it was too late. There are many paths to success!
- yawaramin 9y agoNot at all. But you need to specialise and master a chosen sub-field. Like, I consider myself a programming languages guy because I love type theory. Others love exploring functional programming, OOP, Rust, or whatever. Whatever you like, just get into it and explore, and try to build and ship cool stuff if you can. Everyone has periods of low productivity, you just need to roll with the punches and keep learning and building whenever you can.
- amorphid 9y agoI got my first real programming job at age 40, and had only seriously started programming a few years before that.
- JeremyNT 9y agoI got my first real programming job at 38. It's never too late if it's what you want to do. In my case, I learned how to program when I was much younger but it was never actually my job - or at least, not the primary component of my job. I kind of backed into it, writing more complicated scripts which helped automate what I was getting paid to do, until I eventually just got a "real" programming job. The big thing I think I have in common with the OP: I always try to automate every task possible. This can allow you to add value for your organization above and beyond whatever primary task they hired you to complete, and any company worth its salt will recognize that contribution and try to find ways to help you contribute more elsewhere too.