Ask HN: Am I the longest-serving programmer – 57 years and counting?
41–50 of 555 posts
Re: Ask HN: Am I the longest-serving programmer – 57 years and counting?
#42Where do you work now? And also, I've heard that at Google for example, there is prejudice against older programmers? Have you experienced anything like that?
Re: Ask HN: Am I the longest-serving programmer – 57 years and counting?
#43Re: Ask HN: Am I the longest-serving programmer – 57 years and counting?
#44Re: Ask HN: Am I the longest-serving programmer – 57 years and counting?
#45Could you talk more about what you remember from your time at Mitchell Engineering Company? You worked on order processing and fulfillment...what was lacking in their process that they wanted to computerize? Was your project deemed a business success? Were you happy while you were working on it? Was it just you or a team?
Re: Ask HN: Am I the longest-serving programmer – 57 years and counting?
#46given the numerous posts about age discrimination on hn, i'm delighted to hear your story and wish you many more years of happy programming. as a whipper-snapper 40-something developer, it gives me hope and motivation.
I think if you're a top-tier developer (which OP seems to be!) age discrimination may not be as much of a factor? If you're decent but not amazing (most of us honestly) you may find it easier to find work at 35 than at 55.
Re: Ask HN: Am I the longest-serving programmer – 57 years and counting?
#47What do you think the biggest shift for day to day programming was for you in your 57 years?
Re: Ask HN: Am I the longest-serving programmer – 57 years and counting?
#48Congratulations on being in that company, and may it long continue.
Re: Ask HN: Am I the longest-serving programmer – 57 years and counting?
#49There are probably many of us who will probably follow in your footsteps. Provided that Stack Overflow continues to exist, I have no plans to ever stop programming either.
Re: Ask HN: Am I the longest-serving programmer – 57 years and counting?
#50This would be convenient because the 32-bit signed time_t apocalypse is in early 2037. :-)