This is fun. So much to unpack. Honestly if I'm still an employee by the time I'm 35/40, then I messed up somewhere. That's sort of admirable as an ambition f

This is fun. So much to unpack. Honestly if I'm still an employee by the time I'm 35/40, then I messed up somewhere. That's sort of admirable as an ambition for a founder, but I don't think you've thought about your attitude to age from the perspective of your employees. Have they messed up working for you if they're over 35? Does your attitude mean that any one over 30 should consider working for your company as a temporary gig that they won't stay in for more than a few years? That could have a seriously adverse impact on your ability to hire senior devs. Your memory certainly isn't going to improve with time The basis of my job isn't "remembering stuff". Google augments that ability very well. My skills are applying my experience and combining it with knowledge. I have forgotten loads, but the important stuff tends to stick. You've most likely got less stamina too. This is definitely true, but I also have 25 years experience of making sure I do things in the laziest way possible. I automate loads of things. I document everything. I don't really need stamina, and as a bonus (for me and the company) everything ticks along nicely when I'm asleep. Assuming the outcomes are the same, would you rather run a company where the youthful devs need to run around like their hair is on fire, or one where the sleepy old dev does very little work? For the sake of argument, imagine how well things carry on if the devs leave. Statistically speaking you're less likely to change your mind on any subject In my experience younger devs tend to think they're right more often than older devs, and find it harder to see the other side of an argument. I think it's likely not to be directly age-related though. It's more a matter of seeing how often you're wrong, and that takes time. Now, get off my lawn.