4 ms·
I'll be 59 at the end of this year. Unlike most of the commenters here, I've been self-employed for the last 20+ years, working on my own open source project, a
by PaulDavisThe1st 4y ago
I'll be 59 at the end of this year. Unlike most of the commenters here, I've been self-employed for the last 20+ years, working on my own open source project, and so I have not had to interact with interviewers or companies that might or might not want to hire me during that time. The folks I do collaborate with are generally fairly anonymous unless they stick around the project for a long time, at which point nobody really cares much about anyone's identity or age.
My experience of coding-while-aging has mostly been centered on just a few things independent of industry ageism:
1. smaller working set size: I am fairly sure that I just cannot retain as much design and/or code in my memory at this point as I could, say, 10 years ago. It's a little hard to tell, because the scale and scope of the project itself has grown. But I remember when I could relatively easily think about the entire codebase, or when I knew the answer to any question about the codebase without having to look at it. Those days are over. Interestingly, my main collaborator is about 10 years younger than me, and to a large extent he can still do those things, which reinforces my belief that memory limitations are what is driving it.
2. FOMO: not money, but technology. I look out on the landscape of "the new" and wonder if it is possible that it actually contains anything that would make my work or my project better, easier etc. So far, the answer is a fairly solid "no" - realtime audio software has so little connection to web-centric application development that it's not that hard to be fairly confident about this. But things like Rust still make me wonder if it could potentially do a better job of providing memory safety than the somewhat ad-hoc solutions the project has adopted (in C++) over 20 years. And a couple of weeks ago, someone built VCV Rack with emscripten and thus got it running in the browser, which seems right on the doorstep of what I do. Should I be thinking more about that, or is it a diversion? Hard to know, and only time will tell.
3. Work/life balance: working for yourself on your own project is hard to beat, but finding the boundaries between work and the rest of life can be harder still. Getting older, with a spouse that entertains some ideas about how that means a (slow) shift in priorities, makes that challenge seem even more important. I was lucky that I got to be a stay-at-home parent when my kids were young, but now that I'm closing in on 60, the question about what work means, what work is for, how much I could actually live on, what I actually want to do with my time have gained increasing significance and weight. The answers, alas, are as elusive as ever.