Also it must be weird going to a retirement party for someone who is 15 years younger than you :D
I made a bunch of lifestyle choices (lost weight, keto diet, being more active, less screen time at night, etc). As a result I've noticed a significant increase in energy levels and mental clarity.
> Not OP and not in their age group
Then why are you answering?
I had similar reconnaissance but now I hesitate to share. But challenge accepted, worst case is downvotes :) 4 years back, maybe 5 I used to think this is how old age was (would not mention my age but it is younger than the main OP), body slowly unable to do what is used to be able to do. Then after 2 stents and change in lifestyle, I find I can do same or more than what I could do 5 years back, maybe a decade back. Will it continue like this for next decade, or the decade after that? Who knows? But there are many things within the that are in the range of probability and it is on us to push towards the higher end of the range. For those who start disciplined, it may not make much of a difference, but think of an average person ... I think programming at 70 should be feasible for most as long as they fixed their lifestyle by 50. [Most but not all because this is a game of odds]
What kind of change in lifestyle made such a positive difference for you?
The bad side effects: focus. There are times when you are in the zone and you want to finish some piece of work, and the watch tells you to get up because it is 50 minutes after the hour. 2 very conflicting needs: moving for health vs sit and focus. If I was not overthinking of health, I would rather focus and get the job done in one sitting.
Lockdown has given me a couple of months of sitting in one place. I've really enjoyed the focus and productivity, and online conferences I couldn't have attended otherwise.
But my usual exercise is to walk around town extensively, and to pace a lot while thinking. Not much of that happening while confined to a small space.
Like in politics, there are different camps in terms of nutrition and DIY well being. You follow what works for you, but the best in terms of "pitch" I liked was Dean Ornish and he wants you to focus on a) diet, b) exercise, c) meditation, and d) social connections. All of that is needed, and all of that helps.
Uh, vegies are mostly carbs?
But after they sold the house (he loved gardening) and moved into a condo where there is little to do she can see him going downhill month by month. Before he had a purpose in his life (gardening and house maintenance), now he just has the sit around or go on bike trips. It is a shame.
Many retired people need help with what others consider everyday (monthly, yearly) tasks: changing filters, fixing a door, light bulbs, or minor electrical fixture/switch/appliance repair, stopping ants entering the building, a leak in the ceiling, etc. Fixing PC problems counts too.
Anyone who has owned and maintained a home is capable of doing these things provided they're in good health. I'm always happy to help my retired neighbors with their little problems, perhaps b/c I don't have enough of them and they are an interesting distraction, as well as making me feel helpful.
There're lots of older / retired? people at a library here where I live, two evenings a week, meeting younger people (say 15 to 35 years old) who recently moved to here, with learning the local language and school work.
There're younger volunteers too, helping out with the language, maths, chemistry etc — but I was surprised to see that many older & retired people, maybe 70% of the volunteers. (This was before the virus, now I think libs are closed.)
Just like you can do a 3km/2mi leisure bike ride, or bike ride for strength (eg sprinting uphill) or endurance you can do the same with gardening.
I am also guessing you've never covered any serious area with a garden hoe. :)
It’s also why leaving your job or moving to a place with less activity can accelerate decline. Unfortunately, brains are also very sensitive to depression at an advanced age (less blood flow among other things), so grief/loneliness etc can quite literally cause deterioration. Another reason IMO to make sure seniors can work if they want to.
I'm a young guy (31) but the class was so cool. People from ages 25 to 90 year old Stanford alum.
Actually, now this is hard to take - but when I was a kid in my home town, there were still a couple of civil war vets alive in the local hospital. How is that for something crazy.
The absolute worst thing you can do is retire. That is the beginning of the end. I will work until they plant me.
I do me too (since I was about 30). Not exactly 04:30 though — sometimes I get up at 02:00, sometimes 06:00 ... working 4 - 10 hours, then siesta for about 1 hour.
I find that with a 30 min or 1.5 hours? power-nap/siesta, my brain "resets" and I can stay concentrated 10 - 12 hours a day.
Edit: Now I see that you're in bed 8:30 PM. I first read 8 AM and assumed that that meant a power nap. — Seems I get tired a lot sooner than you.
Do you feel like you learned from your advisors, some if whom I'd imagine were younger than you?
Did you study an area related to your work at the time? Or did you use it to learn a new area?
Disclosure: I am taking my 6th course of 10 as a current student in that program
Likes:
- It's very affordable. My company's education reimbursement is able to cover the whole program.
- The courses are rigorous and I don't feel like I'm retreading very much from my undergrad.
- I'm going to end up with a degree from a top program that is exactly the same as is granted to students who attended on campus.
Dislikes:
- The course selection is a bit limited. Some of the classes that I want the most are only available on campus.
- Slack and Reddit are active, but I feel like I'm missing the social aspect of being a student.
- Some people are skeptical of the online format, which is frustrating sometimes.
It is hard for me to say if the program would be worth it for somebody with an undergrad degree in CS. The cost of the program is incredibly high and I walked away from the program with ~$80k in loans (could have been a bit less but had to take more in the beginning to be able to support my wife as well). I'm also not sure how rigorous the program is compared to others.
This is a really bad reason to do a degree, if you want my unsolicited opinion.
Never seen that one before!
Walter H. Schottky's grave in Pretzfeld says "Prof. Dr. Dr. e.h. Dr. e.c. Dr. e.h. Walter Schottky"
Why do you think it'd be unusual to learn from someone younger than yourself?
I think as an internet generation we are the first ones to experience decreasing importance of the age.
Actually taking Internat based courses now takes a lot of self discipline. Far too easy to slack off and do something else.
I remember paying about $12 a credit a long time ago and that was difficult. These days, I don't know how normal people can afford to go to school. You get yourself deep in debt for student loans you can never pay off. I don't know how that can be workable.
After 50+ years of structured work people forget how to be in charge of themselves.
And there's nothing wrong with that.
I mean I don’t hate my job but damn I’d just sit in front of the TV and go for walks if that was an option.
I learned python a few years ago and have experience with several other languages as well. Python is perfect for someone like myself. To me it is a thing of beauty.
I read a lot - history and biography mainly. Favorites: The Fatal Shore and Empire of the Autumn Moon. Travel 2-3 times a year. Been to Europe, Asia, Africa, Australia, South America as well as all over North America. Favorite place? Singapore.
Walk 2 miles+ a day.
Am a top backgammon player on ZooEscape.
Been married 51 years today and been blessed with 3 great kids.
Not rich but comfortable. Always been a saver or what my sister calls a cheapskate.
Am definitely slowing down. Am more cranky. And think the world is going crazy. Other than that life is better than I expected it would be at this age.
The prospect of just sitting in front of TV and going for walks is horrifying. For short breaks, sure, that's really nice. For years? Horrifying.
Solving technical problems is vastly more satisfying than that.
It's like maths to a mathematician, physics to a physicist. Why would they ever stop, given freedom to carry on?
I would love to be able to retire for the freedom, but with that freedom I would want to build technology, much as I do now except I'd choose the things (and they would be much better things!)
(It might be that the kind of programming you do in your job is a very different thing though. I'm not excited by writing more business forms either. Programming is an extremely broad term these days.)
Can you acknowledge that solving technical problems for decades is just as horrifying to me? And that watching TV and doing nothing is extremely satisfying to me?
But now users are asking me if this is ok. Obviously it's extremely far from ok, if true, so I need to ask: is it true?
I'm curious though - do you think you'd be fine with only doing walks and TV for 40+ hours a week? Personally I got interested in computers and programming very early, and at first it was 100% a leisure activity. It stayed at roughly that level of exciting for me until probably 6 months to a year into being employed as a developer, but it's no longer the #1 thing I like to do when I'm not at work. My current situation is work with a side of typical relaxation (watch tv, browse the internet, etc.), but I expect when I eventually retire I'll start spending a bunch of leisure time on programming and general messing-with-computers stuff again.
I took 3 years off from working (lived frugally off savings) and that is basically all I did. Purposely avoided anything that would be considered “productive work.” I mean I read some books and rode my bicycle, too. But my time was pretty much just watching TV/movies and laying around.
Best time of my life by far.
I cringe when I tell someone about it and they are like, “oh but didn’t that get boring?”
Freedom to choose is what it's about.
I'm really glad you got to enjoy those 3 years.
That does sound like heaven. Watching TV all day does not.
Do you mean family like parents/relatives harping from a distance? If so, they’re just jealous and aren’t worth listening to. As long as you’re smart about your money and make a plan to get a job before you’re tapped out, go for it.
Of course, I'm completely happy to acknowledge that!
I know some programmers who were pretty hot, but one day they had enough and never wanted to go back into it. Good for them, hopefully they found something else they enjoyed.
What I was addressing before was:
You seemed to express skepticism that someone else finds programming something they would actually prefer to do, over retiring from the field, unless they are institutionalised or imprisoned, like some kind of sick creature.
So I added myself to the data, along with mathematicians, physicists etc. to support an argument some may relate to, to say it's not that unusual for people to actually love programming or other intellectual activities like that.
I should have included artists and writers. The motivation is a lot like it is for them: It feels innate, like an instinct, it just makes you miserable if you don't pursue it.
I assure you, if you could see the messy diversity in my life, you would not think of me as institutionalised, or particularly structured :-)
The idea that you only do things because it is your job suggests a limited life, I remember when I was working telling the others about all the trips and cruises I did on my time off. When I asked they what they did on vacation they always went to the same places year after year. I guess that is what they wanted.
Thats fun for the first week. The second week its depressing but you still do it. On the third week you will be picking up hobby projects and working on them just for fun.
For example, of you love rocket science and working on rockets, you're probably better off working for NASA or SpaceX.
Nothing really.
I guess what the parent was getting at was that if you are an employee at a point of your life when society expects you to be retired, then you will not be able to allocate your free time as you see fit. In other words, working for others past retirement means you never really retire enough to indulge in things you never had time for in your prime, like spending quality time with one’s spouse for instance [0].
[0] Google’s former highly-paid CFO decides to retire after working for nearly 30 years consecutively https://mashable.com/2015/03/10/googles-cfo-retires-memo/
In other words - one might want freedom, basically.
As for not helping someone - programming can be recreational, just for the sake of enjoyment.
I finish projects when they're for work. Or at least, I stay focused.
My own hobby projects are more fulfilling to me, but I often put them aside for long periods - sometimes years - because I don't need to finish them to get pleasure out of doing them, and it's much harder to stay motivated to finish the often very boring parts when I don't have to.
But it feels good to finish things up too. I can push myself to do that for side projects, but the time and energy it takes to get me motivated to do that when I don't have the external pressure to motivate me is much harder.
If I "retire" I'll probably have to do a startup again to have some of that pressure...
Retiring to millions may be true in theory for certain programmers, but certainly not true for all programmers.
Reality is often different for everyone. As the African proverb says: “all fingers are not equal” meaning the outcome of a specific situation can differ across people. For instance, what if s/he had a financially draining medical emergency, forcing them to rejoin the workforce?
And then what? Believe it or not, some people consider programming a blessing and fun. If it keeps you engaged, why not continue to get paid for it?
I'd love to spend months reverse engineering proprietary electronics and writing open source code / datasheets for them.
Not everything is great: the procession of silly methodologies, the endless train of obviously doomed technologies, and the recent obsession with social justice appearances. But the core of tech is still ripping good fun.
Sometimes too, I see comments from people frustrated with having to "work so hard". I'm sorry they have that burden, but for me, programming is not a negative in my life -- even though often times I do it many hours more than is actually asked of me. Sure it's got it's boring/frustrating times, alternatively it can be very difficult, rigorous, and taxing, but I doubt I'll ever completely put it down.
As a twenty-something, I'd love to work along side an "old timer". Many of the abstractions and technologies change in our field, but just as many foundational concepts stay constant. I'm sure I would learn so much.
Best of luck to you.
My grandfather was a (fighter)pilot and later he worked senior management at a bank. His biggest regret was not going to uni himself(poor parents and the army paid for it), later that my mum didn't go uni (she became a teacher) and after that even his grandson didn't get a degree.
Hopefully I can follow it online and I can speed up the lectures to 1,75x :d
I'm around same age and experience, though I'm actually getting a degree now. My advice is - don't. It's an unbelievable waste of money and time. My initial goal was to leverage the degree into a better job but my plans changed and now I'll just be left with a useless piece of paper. In any case, getting a degree once you retire would be even worse. Work on some real world project that you enjoy, rather than settling for doing menial tasks, doled out by people who may know less about the subject than you do, while being rewarded with virtual points/grades.
The degree itself isn't useful but it did make me take a few classes I wouldn't have otherwise. I took physics 101 in person and absolutely loved it, I took art history online and didn't expect to like it but it turned out interesting.
Assuming you can go somewhere where the credits don't expire I suggest taking one class a time when you have time available. Read the rate my professor reviews and look for the good teachers. Most of the time online is fine but don't be afraid to take a class in person, lots of older students at night classes.
Serious question. Why? I love coding; I'll probably code as long as I live, but I can't imagine tying myself down to a full time job beyond the point where I need the money.
Kudos to you for not losing your passion for the job!
One question: Do you go through a mid life crisis in programming in your 40s/50s?
My story (just felt like sharing): I am in my 40s and have been programming for 30 years (I first wrote in Fortran in my Engineering College, 1st semester). Later professionally coded in C++ for around 10 years (and still keep coming back to it, as needed). Java for 10 years. Golang for 7 years. And Python for last 2-3 years. And there were other languages like Visual basic (late 90s). A lot of Unix shell scripting. I still think, I am at my best. But do have occasional self doubts. The main difference from younger days, which is perceptible to me, is the need for eye glasses, and needing slightly bigger fonts on occasions (HN is perfect that way).
I teach/guide my elder son, in programming, who just turned 20, and doing well as a programmer - did half of K&R C chapters and decent in algorithmic programming. Spent few months at Codeforces website and reached specialist level (Next level is Expert, which is generally considered respectable by any standard). And he also likely lurks on HN. :)
So now, when I see your message, it only makes me happy, that HN has likely at least 3 generation of programmers if not more.
[1] https://news.ycombinator.com/user?id=lutusp
Edit: typo
I used GraFORTH and TransFORTH so much...
I'm in my 50's now, started my career during college, writing educational software for Apple II clones (not in FORTH, sadly). Now mostly Python, since the early 2000's, with little bits of other languages here and there.
I find HN delightful for the diversity we see here.
> genedangelo 1 day ago
> The one thing that comes to mind is to avoid the "hammer looking for a nail" syndrome. I see this all the time, especially in academia. Rather than worry about learning all the latest stuff, concentrate on solving the problem at hand in the simplest and most effective manner. If that requires you to learn new things, then that's a great time to expand your repertoire - working on a specific problem. Of course you have to strike a balance, but mainly concentrate on solving problems rather than being up-to-date on all the latest stuff and trying to find the proverbial nail for your new hammer.
Additionally, I am in a coder in my 50s and I have to say I am not going through any kind of mid life crisis in programming!
Like genedangelo, I just focus on problems that need to get solved and I really don't care how I solved it as long as I use a great tool that is meant for that job.
Super happy to learn a new tech if it makes sense for the problem.
There was a phase a few years ago where folks were using node.js to build all kinds of websites, including content heavy text based sites that would be better served as static html or dynmaic Ruby, PHP etc.
I think that's the classic mistake of a hammer looking for a nail and I can imagine it was really unsatisfying to build those kinds of sites with that kind of tech and might even contribute to burnout (just speculating).
Just to clarify, I am also not going through a crisis as such, thankfully. Just a doubt on future continued ability lingers on occasions.
What you say, makes sense to me. After a few decades, we just see some patterns repeating with different names - RPC -> CORBA -> RMI -> Web servcies (based on SOAP) -> REST (based on JSON) -> Google RPC (going again to binary style) ... and so on. Not being cynical. Things progress in a way, but also have echos of the past.
Delighted to read these stories about even-older-than-me old-timers. Even though I am a relative spring chicken, I'll list my old-timey computing experiences:
- Started programming on programmable Wang and Monroe calculators.
- PDP-8m in high school. 12k 12-bit words for four terminals running Basic. By special arrangement, I could take over the whole thing and use FORTRAN.
- IBM-370 in college, and I spent lots of hours on an IBM 029 keypunch. (That's where I developed my love of loud, clicky keyboards.)
- First job with Datasaab (yes, a computer division of Saab), and I programmed in their weird DIL-16 language.
- PDP-11 in grad school.
- Various VAXen in my early working life. Picked up Emacs in 1985 and now it's in my fingertips.
- A buddy and I wrote a book intended to support people who needed to work with a large variety of computing environments, (a real problem my buddy encountered). It was instantly obsolete, as it was published as minis were dying and PCs were becoming dominant. (https://www.amazon.ae/Computer-Professionals-Quick-Reference...)
- Many years in startups, mostly in Unix/Linux environments.
Retired now, but still enjoying programming. Having a blast with my current project: https://github.com/geophile/marcel.
I don't think this means the dreaded 'emacs pinky'...
Congratulations on being in that company, and may it long continue.
Or perhaps I'd classify him as the somewhat more sycophantic "longest working genius" or "longest working cool guy". Heck, Knuth was uniquely awarded a master's degree for his bachelor's because his work was considered so outstanding, he's an organist and composer, and he's hilarious. I love this quote about him: "If you had an optimization function that was in some way a combination of warmth and depth, Don would be it."
A quote from him in an interview I found: "Indeed, as mentioned above, my life's work was to be a teacher."
But being a programmer and a computer scientist -are- two very different things. Simply in his daily activities over the last sixty years, Knuth has been writing tens of thousands of pages, doing a lot of math, diving deep into computer science topics. (That is not what I do in my employment as a programmer.) This guy has been sitting behind a keyboard and writing code. (That is what I do.)
But being a programmer and a computer scientist -are- two very different things. Simply in his daily activities over the last sixty years, Knuth has been writing tens of thousands of pages, doing a lot of math, diving deep into computer science topics. (That is not what I do in my employment as a programmer.) This guy has been sitting behind a keyboard and writing code. (That is what I do.)
Depending how and whether you count academia, Donald Knuth may have a slightly longer career: https://en.wikipedia.org/wiki/Donald_Knuth
Feels like a decent chance you're third, then. Certainly you're one of the longest-working programmers. Best of luck. :)
And I think I'd classify Knuth as the slightly different "longest working computer scientist". He's known for his quote "Beware of bugs in the above code; I have only proved it correct, not tried it."
Or perhaps I'd classify him as the somewhat more sycophantic "longest working genius" or "longest working cool guy". Heck, Knuth was uniquely awarded a master's degree for his bachelor's because his work was considered so outstanding, he's an organist and composer, and he's hilarious. I love this quote about him: "If you had an optimization function that was in some way a combination of warmth and depth, Don would be it."
Having said that no matter what role it's good to code everyday.
Funny that there’s an error in that sentence.
Here's my own thought. My last place of work did a lot of research into teaching and simulation tech, and was heavily pushing AR / VR solutions from a disruptor perspective. Some of the theoreticians were heavily into their generation X/Y/Z perspectives and made a lot the advantages that young people would have as 'digital natives'.
As someone who'd been using computers since before they were born, I was quietly amused as being characterised as someone who couldn't properly understand tech because I didn't program until I was age 17/18. It could be argued that many modern digital natives are really the locked-in inhabitants of digital cities and walled gardens. I now characterise myself as a sort of 'digital settler' who in retrospect could be viewed as a pioneer on the digital frontier (although this is not how I perceived it in the early 80s when I was learning Pascal and then C on DEC, Amdhal and Vaxen).
I think my message for people who want to stay involved with the tech is to decouple their enjoyment of it from their career aspirations. Of course, YMMV!
So true. I am lucky that almost all my programming is for personal enjoyment/growth and have gotten a huge amount of pleasure from breaking out of the infinity of abstractions that make up modern operating systems and getting into electronics and microcontrollers (which can now be purchased for pennies). There’s something great about truly understanding a system (also true about larger scale and even non technical systems, but I have particularly felt the change you describe from pioneer/settler to controller citizens on modern computers).
Thank you for your words! I hope to retire soon from headless chicken corporate job and to bring back a joy of programming art.
Any advice (technical or life) for us younger people?
Maybe I'm biased? PHP paid my bills for a long time and currently I'm a front-end developer that works mostly with Angular (but sometimes I jump into the .NET Core backends). I love JS and TS, they evolved nicely along the years.
Nothing against being a fanboy for one specific lang, but thinking "X" language is bad/joke/nightmare isn't nice and makes people that work with them look like losers, which they aren't.
To make a JS package consumable by a reasonably strict TS project, someone has to basically rewrite the package. It's less effort than writing one from scratch, but it's not free.
I’m not sure what you mean by “strict” here... Certainly one can use JavaScript from TypeScript, and even provide type information for the JS with declaration files. [1] Does a “strict” project require something beyond this?
[1] “Declaration Files”, TypeScript Handbook https://www.typescriptlang.org/docs/handbook/declaration-fil...
Adding the actually correct and reliable types is the hard part. (But easier than writing the code in the first place.)
'1'+1=2 prevents a lot of errors. The languages tries to help you along compared to an harsh error. Maybe you want a harsh error.. halting everything until you declare a new variable with the same type and have to go through a manual conversion. For me let the language handle that. If you are tdding anything unexpected will be caught anyhow if you are worried how things convert.
It's like rust in terms of memory management vs c. It handles it for you..
* safe/unsafe
* strong/weak
* static/dynamic
Note that while safe/unsafe is basically all-or-nothing, strong/weak and static/dynamic are more of a spectrum, so JavaScript would be safe, weaker, and more dynamic than other languages. Typescript makes JS stronger when authoring code.Still, this is unforgivable in my book:
[] + {} == "[object Object]"
{} + [] == 0 Array.prototype.toString = function () {
return '[' + this.join(', ') + ']';
};
It would be convenient if Object.prototype.toString by default threw an exception, since the default breaks the embedding rule I described.The second example is misleading, and it has nothing to do with the rules for addition: the {} at the beginning of the expression is parsed as a code block, played off the rules for what the value of a Javascript statement is. More realistically, we have
({}) + [] == "[object Object]"
but the original is, effectively, {
}
console.log(+[]);I worked with PHP professionally for some 10 years, with very competent colleagues from whom I've learned a lot. The PHP ecosystem with Composer and Symfony components is quite good. Still, PHP itself is a terrible language. I have less knowledge but a similar opinion of JavaScript. Doesn't mean people working with PHP or JavaScript are losers - I admire their tenacity and do feel a little bad for them.
Is COBOL terrible or C Or Go?
> Terrible compared to what?
Terrible compared to other available programming languages.
> What do you find a better language?
Lisps, Haskell, Erlang, Rust, but even eg Python, Ruby, C, Java.
> What makes a language terrible for you?
Allowing me to do unreasonable things and resulting in unreasonable behaviour. Eg JavaScript:
[] + {} == [object Object]
{} + [] == 0
> Is COBOL terrible or C Or Go?
Programming languages are products of their time and context.
When COBOL was created, it might've been the best there was. By now, I think COBOL can be considered worse than many alternatives. If someone decided to write a non-toy greenfield project in COBOL today, I'd be surprised and might question their sanity.
C has two things going for it: it's a simple language and it's close to the hardware. I wouldn't call it terrible.
Go, now I really dislike Go, but I think there might be situations where it's the right tool for the job. Simple web services perhaps?
PHP was terrible already when it was created. I don't hold that against Rasmus, he just wanted to get simple things done, and didn't even intend to create a full-fledged programming language.
JavaScript... Brendan Eich wanted to put Scheme scripting in the browser, but because Java was popular, he was told by management to make it look more like Java and also to call it JavaScript. Oh also he had like a two week deadline or something.
Yea, I dunno... good hard questions :)
I don't particularly care about php because I have basically zero experience with it.
Any meaningful milestones along the way, that you think are worth noting. Tasks or roles that indicate progress?
I'm not so sure about that (but I'm pretty green on bioinformatics). I mean, for one: https://xkcd.com/1605/. For two, if that was the case we wouldn't need projects like folding@home and such to tell us what the structures described by DNA actually look like. And for three, there is a massive amount of influence on brain development from elsewhere (both from within the fetal body and from the womb). It's a bit like having a compiler's source code but nothing to bootstrap it with...
I, too, have been programming for 32 years. I have thought about your question many times. My current solution is to 'play more'. Allow yourself to play, even when you are in the 100x additional part. Playing makes your passion flare up again. By play I mean to start interesting side projects, ideas, try something new.
So 1) you benefit from the work by having fun 2) others benefit from your work by using it to solve their problems or building things they find fun
Usability is also a problem worth solving. It's just a different problem.
Good luck and thanks for a great post!
(Anyone else who'd like this alpha feature turned on for their account is welcome to email hn@ycombinator.com and we'll be happy to.)
[1] https://nolt.io
No affiliation, I just use a site which uses this to provide functionality suggestions. I don’t see why this kind of functionality can’t be bootstrapped from existing HN code.
i am definetly interested in this one. i often search for timestamps to find newer comments. color markers would make that a lot easier.
Of course, it exists. If you are over 40 and go on an interview where the interviewer is a 20 something kid you know what I mean.
My approach to age discrimination can be summed up this way.
Screw them. I have more experience and knowledge in the field than 99% of the people working in it, especially the managers. And I project that in an interview. I don't give a crap what they think of my age and I make sure they know that. I have what they need and they would be better off recognizing that.
Does that attitude work every time? Of course not. But I will be dammed if I will be submissive and put up with age discrimination. To hell with them. If they don't give me a job, some with better sense will.
The key is NEVER GIVE UP.
I would love to hear answers to the following:
1. What ideas proved useful throughout your career, and what ideas did you change your mind about?
2. What are your hobbies? Do you still program in your spare time - if so, what? Or do you find other outlets?
3. What went into the decision to go back to school? Did you get the PhD? If not, did you get burned out, or what lured you away?
4. What were the Big Ideas in software over your career that didn't work out? Any that were better than expected?
5. General successes/regrets/advice for these readers!
> What ideas proved useful throughout your career
Learning Lisp. I got an enormous amount of leverage out of that, and still do (I'm more or less retired, but I have a nice little Lisp consulting gig at the moment).
> what ideas did you change your mind about?
Before Lisp I thought BASIC was pretty cool (old-school BASIC, with line numbers). I was pretty down on Python when I first encountered it but now I'm a fan.
> What are your hobbies?
I like to hike, bike, ski, travel, fly airplanes, free dive and ride flowriders. I also write a blog.
> Do you still program in your spare time - if so, what?
Yes, but not very much. The last big project I did was writing the firmware for this product:
and the e-commerce system I use to sell it. That was quite a while ago.
> Did you get the PhD?
Yes, because I thought I wanted to be a college professor. Turns out that's not what I wanted, but I'm still glad I did it. But it's not for everyone. It really depends on what you want out of life. Do it because you love research. Don't do it as a means to some other end. It takes way too many of the best years of your life to do it for anything other than its own sake.
> What were the Big Ideas in software over your career that didn't work out? Any that were better than expected?
I've seen a zillion software fads come and go. UML. XML. ISO whatever the fuck it was back in 2000 or so. The vast majority of popular things in the software world are bullshit. The world keeps re-inventing s-expressions with different syntax. Very little has turned out better than expected, though Rust and webassembly look pretty cool. If I were going to do another deep dive into something today it would probably be one of those two things.
> General successes/regrets/advice for these readers!
The world today is awash with computational wealth beyond the wildest dreams of my youth. Take advantage of it. Get a Raspberry pi and noodle around with it. Bring up a web server, an email server, a DNS server. If you're really feeling ambitious, write your own, or write a game. Build a Linux kernel from source. Design your own programming language and write a compiler for it, even if it's just a minor riff on something that already exists. None of these things are particularly hard [1], and the things you will learn and the empowerment you will feel by doing them are priceless.
[1] The hard part of programming is not getting things to work, the hard part is getting things to work well enough for someone else to want to use use.
The nature of the illness varies somewhat over time. The panic attacks only seemed to happen when I was in a room with a large group of people. So quitting school largely removed me from those situations.
I was diagnosed as Bipolar 2 in 1997 by a psychiatrist in Manhattan, where I was living with my girlfriend. I started having true bipolar symptoms in USAF Basic Training but made it through (talk about rough), then years later working as a developer, I got to a point where I could just not deal with people. One of the signature characteristics of bipolar (and other similar disorders) is some form of paranoia. People at work would make some mild critical comment and my head would be spinning for days full of anger and fear and pondering what I should have said. The NY psychiatrist asked me just a few questions: 'When was your first clinical depressive episode' (19), and 'are you second-guessing yourself a lot' (Yes. A manifestation of paranoia as noted above).
How did I ultimately deal with the disorder? Wonder drugs! Zyprexa since 1997, Wellbutrin for many years, and lamotrigine, a mood stabilizer. Being bipolar is not something that I notice much anymore.
One thing I would mention for anyone who is listening and suspects they are bipolar: Bipolar people are vulnerable to trauma and PTSD. What helped me was another miracle (IMO), EMDR. A single one hour EMDR session with a trained therapist can rid you of trauma that would take a year or more of talk therapy to accomplish.
Hope that was not too long-winded.
Thanks for that particular datapoint, and for the info.
Either that or I just doxxed myself ;)
what technologies is your grandpa using?
what's his opinion on javascript?
any epic kids these days stories?
Edit: One more thing is that he’s the most intellectually well-rounded person I’ve ever met, a characteristic which I wouldn’t be surprised if it was common in programmers with more than a couple dozen years of experience.
I wager, everything will be retroactively doxxed in about 20 years or so...
I have been writing software since 1983, and Apple software since 1986. I started as an EE (actually, technician, but became an EE in '84).
I was a manager for a large part of my career, which relegated my programming to open-source projects (one of which has become a rather significant force, in its own right).
I also worked for a Japanese corporation for almost 27 years. The Japanese have a sort of "reverse-ageism" in their culture. Older folks are often treated with a great deal of respect, and their judgment is considered valuable. Many promotions have age (must be "at least"...) as a factor. There's lots of issues with Japanese business culture, but it was the environment where I learned a lot of my cultural cues.
So, it has been rather...interesting to encounter the current...um...level of respect...for experienced engineers in today's American tech industry.
TBH, it was shocking. I knew that it was a factor, but I had no idea that it was so prevalent. I was absolutely gobsmacked.
When I first encountered it, I just wanted to throw in the towel and run, but I don't work that way. Instead, I doubled-down, and it has been quite gratifying. I guess old dudes can code, after all...
Again, you have my respect.
This guy is inspiring: https://www.businessinsider.sg/oldest-nobel-prize-winner-art...
But yeah, always vaguely thought she was younger starting.
(Aside, I wonder if recruiters in 1944 were already asking for ten years of ENIAC experience?)
"We shall need a great number of mathematicians of ability; there will probably be a good deal of work of this kind to be done" - Alan Turing, 1945.
You might find this talk by Bob Martin interesting - https://www.youtube.com/watch?v=ecIWPzGEbFc - it's a history of programming that isn't the usual style, but instead about this growth into existance, increasing numbers of programmers, where they came from, and the effects that's had on the industry and on programming languages.
As an example, Larry Page may have been a programmer in the very early days of Google, but it's been more than 15 years since Larry has seriously written code for a living.
As opposed to Jeff Dean who is still hacking away at his keyboard.
Welcome to HN! I hope you stick around, it can be a great place.
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.
My biggest piece of advice to anyone who wants a long technical career is to keep learning new things. Don't rely on your day job to train you in what you need. Follow up on stuff that interests you and invest some of your "me" time on staying current in areas that interest you. I've seen a lot of people drop out of the industry because they were over specialised. I know APL experts, Cobol and DB2 experts, C++ with MFC experts, etc, etc. None of them are working as programmers any more. It's tempting to thing that Java enterprise and C# and Ruby on Rails and Python and whatever you think is the best paycheck will last forever. It won't and over time you will slowly become obsolete. A 40 something (or 50 something) with no relevant technology experience will be seen as less valuable than a 30 something because people will be imagining you are simply going through the motions. The fact that you aren't getting sucked into the new (and horrible) programming fads makes you even less attractive because the people hiring you have been pulled into those fads. So it's important to be able to speak the speak and walk the walk.
Anyway that's precisely the problem - either get sucked into all the horrible fads or not finding a job. That's a pretty bad choice.
There would be new projects & not many people in the company experienced in the tech required (due to hiring staff that has experience in their bread & butter current projects) and it was often pretty easy to jump on those ships - it does require the confidence that you'll be able to ramp up quickly!
Also when a technology is new there is a shortage of people with experience using it & companies relax experience expectations when hiring.
Artists get better with age. Programming is an art. All tedious tasks get automated away. All that's left are design decisions. Making good design decisions is what people mean by "taste". Taste gets better with experience.
A young person may have more physical energy, but to paraphrase Steve Jobs, they don't have any taste. Their surplus physical energy could be a liability, as they'll just write more code that's hard to maintain. Of course there are exceptions. Don't discriminate by age in either direction. Ask for experience, and make your final judgment after examining their portfolio (just as you would an architect or photographer), looking for signs of good taste.
Further reading: "Taste for Makers", by Paul Graham, http://www.paulgraham.com/taste.html
That means most employers have only ever seen developers with <5 years experience, working in teams of same, using languages and tools designed by and for same. How could such employers properly value 30 or 50 years of experience?
Does wisdom count in software? Practically and generally, I'd say no. When setting hiring priorities, cost trumps wisdom in all but the most senior roles.
(BTW, at 62, I've been coding professionally for 34 years. I wish I were valued more by my employers with each passing year. But if it's so, they hide it well.)
What your current title?
Of course, if you stay where you are your salary doesn’t, so :/
0: Kilo senior developor (min 10 years) mega senior developer (min 20 years) giga senior developer (min 30 years) tera senior developer (min 40 years) peta senior developer (min 50 years) exa senior developer (min 60 years) zeta senior developer (min 70 years)
> I'm sure certain sectors of the hotshot startup world are biased towards "bright young things" but as far as I can tell there are many orgs that have a place for grizzled greybeards
What kind of organizations are you referring to? / How would one go about finding organizations like these?
The reason I'm asking is that I'm in my late twenties and considering doing a PhD in mathematical physics before leaving academia for good and entering the IT industry. Like you, I started programming in my early teens and while I kept coding as a hobby and also worked as a part-time software engineer for a startup for ~1½ years, I obviously have much less professional experience under my belt than those "bright young minds" who enter the industry in their early twenties. So I'm somewhat afraid that it'll be even harder for me to enter the industry when I'm in my early/mid thirties than it is right now.
57 years is an amazing innings in such a relentless field - congratulations, and long may you continue.
Most of the "interviews" are conducted by very-recent college graduates who know the algorithms and their big-O.
The fact that I taught Data Structures didn't seem to matter as none of them actually read my resume (despite having a copy they brought with them).
It is more of a "hazing ritual" than a job interview.
The first time I said I wanted a pair of single focus lenses for the computer (so I could use my whole field of view..), I got a lot of flak about "you should get bifocals". I haven't needed to drive anywhere in the last couple of years, so I basically never where my distance glasses anymore.
lately though.. Seems like they're getting more used to the idea. Maybe more people doing it ?
I've got the computer glasses, and then the regular ones. I swap as needed.
My only problem is forgetting to change glasses when I go out, and not really noticing til I hit a main road and wonder why the street signs are blurry.
Have you tried the 'blue blocker' type lenses? If so, how do you like them ?
I'm also very nearsighted :)
A true inspiration, thanks for sharing.
Wow, I wasn't even born in 1963 (1965 issue here), and I really got into programming around 15 or so, so 40 years and counting on this end. Super impressive that you still enjoy coding and do not plan to retire.
These days I only code for myself, I've stopped doing commercial work but will occasionally help out in places where my particular combination of talents is useful. I also don't plan on giving it up at all but you never know what the future will bring and I'm very sure that my mental faculties are not at the same level where they were 20 years ago, nor do I get as fired up about a cool algorithm as I did back then.
Being born around that time and seeing all this development has been a ride that I would not trade for anything else except for - retrospectively - a career in music (which still is my first love) or - corny, but timely - being an astronaut. But not to fly circles around the earth. So all things considered I feel both lucky and privileged and I wonder if those are things that you share or would care to talk about.
best regards & a very warm welcome to HN.
So you have ten more years working than I do.
But I look forward to the day when I have accumulated sufficient experience to truly understand Lisp.
May the code by with you. Always.
Congrats on an awesome career. You are an inspiration. Slice up fulfillment data in Fortran II before rules and drama -- legit. What are the younger programmers doing wrong? (I don't think we are much quicker - at anything). Also #1 on hacker news.
The PCs really aren't much more than intelligent terminals. You were right, and you should have held your ground and been eventually correct.
What do you think the biggest shift for day to day programming was for you in your 57 years?
Here's my bio:
When considering going back to school or focussing efforts on writing software for employers/clients, I always side on writing software. But with your story I will give more weight to going back to school, as it might lead to new avenues.
I'm in my 40's and really enjoy these stories from older programmers to help me stay motivated. I like to believe that my best days are always ahead of me, and your story helps me affirm that.
Second, I want to take a moment to commemorate and celebrate my father, who enrolled at MIT in 1967, graduated w a Master's in CSEE, spent 25 years working at GenRad and continued working as a software engineer (at MathWorks) until the week before he passed away in early 2018. So he was a programmer for over 50 years. While I'm unlikely to reach that milestone (having started "late", a couple years after graduating college in 1996), my younger brother wrote his first program at age 5 and is still at it today (36 years and counting).
No particular point to make here, just reflecting on our chosen field and feeling very, very fortunate to be part of this community. Be well! :)
Welcome to Hacker News. They don't always treat us graybeards well so you'll need to be tough.
Why would I go from the top of my skill set (programming) to the bottom of a job I'm unable to perform?
I can barely manage myself some days. And I am not a "people person".
I’m 12 years in professionally and still loving every second of it! Currently been slugging out Leetcode problems all hours of the day to try and get myself to an org with a proper engineering track. So maybe further down the line I still might be able to solve computer problems (in some way or form) during my day.
I really hope to someday to be able to come onto HN and do the same thing as you :)
Hope we both will do the same as what the OP did.
My answer to people who ask me "For how long do you think you can code, you need to become a manager or whatever" has always been "Until I die".
He started as a mathematicatian, and probably worked with computers professionally only after 1963.
Programming in East Germany was .. interesting. For example, they used punch cards long after they were out of date in the west. My grandfather still has lots of punch card origami he did while waiting for his batch jobs to finish.
Congrats to all what you have achieved! :clap:
I once had the pleasure of interviewing a German consultant who was into Android programming and he was like 48 or 50 years old. The interview was like listening to stories of his programming days with various hardware(Commodore etc) and it was fascinating that too with his precise German English accent.
Eventually I plan on getting another masters or a PhD in data science, statistics or some other computer science field.
If I could I'd buy you a cup of coffee and pick your brain. If you went to FAU then we are relatively close.
A lot of people have comfort in their current programming language, and talk down about other languages.. resistant to change. And sometimes they are right because things are evolving too quickly that they could be a fad or become a standard and popular.
Again, curious as to when/how you felt it was a good time to learn something new. And this is specifically geared towards your later years.
I’m in my early 30s. And with technology changing so much, I’m curious if I’ll still be in touch with it all in 30+ years. And how you seemed to accomplish it.
Thanks and I hope I can hear from you!
Do any of the computer museums do that?
My mom used to interview people, mostly seniors, to capture oral traditions, get first hand accounts. I think the process she used was called "oral history". A simple format that any one could use to do their own interviews. She was long time volunteer for our local Swede-Finn historical org. She figured out how to do this once her parent's friends started passing away.
A friend played fiddle and was really into Americana. Most of the musicians were 70+. When they passed, all their lore and many of their songs were lost. So she started recording her friends and capturing their bios, life stories, stories about the music. She self-published a book and cassette combo. Two volumes, IIRC.
Just two examples of what I'm suggesting.
My first job was at Acorn Computers Ltd (UK), writing Acorn ISO Pascal in 6502 assembler, and fast forward almost 40 years currently working for major Telecom writing C++ frameworks/libraries for Linux. Still enjoy it as a hobby too, currently writing my third C++ neural network framework (full blown, GPU accelerated, etc), with lifetime goal of eventually building autonomous robot with animal/human level AI.
I am 47, too coward to kill myself, too terrified to take more shit.
Do you face any such health issues related to the profession? Or do you do/practice anything that can avoid such health conditions related to the profession?
1. Constant complaining about the state of things(too much memory, too complicated, back in my day, blah, blah, blah). Why do I have to learn git?, containers?, on, and on, and on. VMs are just fine, what's wrong with java 1.4?, ... exhausting . These programmers probably sucked when they had 5 years of experience and continue to suck today. Crossed arms, learned helplessness level 99.
2. Crazy life long learners that have ridden one technology wave after another for decades on end. When something new comes out they are on it like flies on picnic food.
It's my greatest, most sincere hope that I have the energy, temperament to become the latter.
> Since then, all my jobs for the past 57 years have involved computer programming
As others have pointed out, there are definitely older, working programmers like Margaret Hamilton [0], but who may not have programming as the main part of their job. Would you say programming is the main part of your day as a data scientist (I have no idea, as I've thought DS could encompass a variety of non-programming work)?
A common question that comes up with mid-career programmers is whether they should take the jump into management – how have you dealt with that crossroads throughout your career?
I am exactly half your age and have been programming seriously for only for 25 years (if we consider talking over serial/COM ports at 1200 bauds or passing printer escape sequences from a DOS ncurses-like software written in BASIC serious :), and I can't imagine not programming in the future. Programming is the art of creating solutions for me, and I am sure you can relate!
However, I do hope to retire early, to allow me to work down the long bucket list of ideas I have.
As with anyone in programming for so long, I am sure you have a similar bucket list :)
Thus, my question is: what has kept you at your jobs?
There 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.
How do you rate your mental agility versus your younger self?
I was honestly curious how it compared. What tools and processes transfer over, that kinb of thing.
You don't type; is the way you create this logic similar to Ladder Logic, Pure Data or Touch Designer?
I just realised I need to walk my dog more often after the lockdowns are getting less strict!
How many jobs have you held, and what was your criteria when switching jobs (apart from any possible family reasons)?
Looking back, is there any favorite technology of yours (language, concept, anything)
Do you feel the industry is buzzword-driven to a significant extent? (e.g. things get rebranded, reinvented, reimplemented on latest tech instead of fixing and improving existing things, business value does not get better but software often gets more resource-hungry)
No disrespect, after only 20 years (third of your time) sometimes I feel that it was much easier to solve things in the beginning, so sometimes I am kind of worried what will happen if I ever live to that age. Generally I am interested how does cognitive ability changes with age.
[0]https://whittleconsulting.com.au/livebook/downloads/3.5-Stor...
Also: 74 - 57 = 17 years of age when you started as a full time programmer. How did you pull that off in 1963?
When I was 17 I started a program connecting high tech firms to winners of a programming competition for high schoolers that is still going, 14 years later :-) But I was far from the first to do this here.
It really boils down to what I've already said. A company is its staff. What its staff does and accepts other staff doing is ultimately its policy. Anything else that they might have written down into a document that isn't enforced or followed is not company policy, but a way to compartmentalize responsibility and blame once its actual policies come under scrutiny
The company (and the law) have rules about discrimination and fairness, but when a group of 20-somethings interviews an older programmer those rules may not matter. Fixing age discrimination probably shouldn't focus on laws and company policies, no company has a policy condoning age discrimination that we need to fix. It's the software dev culture that equates age and experience with "not a good fit," for whatever reason. I have my own theories what those reasons amount to but regardless of why I think it happens, it clearly does.
Welcome to HN! It's a great place, has a few things I don't like here or there, but overall a great place to learn all sorts of things and learn about all sorts of people from varying backgrounds.
Well done!
For example: maintaining the required mental agility needed to do the job, learning new technologies that come and go, overcoming relevant biases, staying relevant as "less experienced" workers seem sufficient to do the same job, etc.
I don't think he was retired.
This would be convenient because the 32-bit signed time_t apocalypse is in early 2037. :-)
Put that in a pitch deck and raise whatever you want!
J/K! Congratulations on the career, success and evolution!
1/ Did you ever feel isolated in a group because of age? 2/ How did you manage to stay focused when your colleagues may just be growing up the ladder?
Tell us, what is the secret to your longevity?
[I'm more than halfway to your experience but definitely missing this aspect.]
Hope I'll be able to say the same someday :-)
I mean - sure. I love Gates and all. But things like the Win32 API make me so weary to ever trust his opinion as a SWE. His technical "blessing" on anything doesn't mean much IMO.
so should be software engineers.
This is truly inspirational, I also plan to keep coding well into 70s/80s, just loving it, or as long as I can.
Am I alone?
Also, it would be wise to name it "genedangelo in byteland" haha! ^_^
Stuff like the comment you answered to is how the people pulling in the actual big bucks hope to get you to work for cheap.
TL;DR everyone ancestor of mine born since 1916 has been a computer programmer.
Attempts at protecting a game client from reverse engineering are mostly a waste of time. These protections can be beaten faster than they can be developed. Once a hacker has reverse engineered your wire protocol and cryptography your game client is just one of potentially several.
Has probably changed a lot over the past decade or so, but the developers at the time were wasting their efforts on tightening their software clients rather than using AI, honeypots and other techniques on the server to detect and ban bots. I recall offering to work for a couple of the companies whose games I had developed cheats for, but they rejected me right away without even an interview.
One of the issues is: MMOs are often very repetitive. The actions of your real users are somwhat bot-like to begin with. This means bot developing isn't that difficult. Adding randomness to the behaviour of the bot can make it look like a regular player. I suspect there are some differences which some well trained neural networks might be able to classify, but you need to be really careful of false positives because anything which gets in the way of regular players enjoying the game will lose you customers.
Selling the bots themselves was an option, but people can just reverse engineer your bot and redistribute it. The bot typically ends up posted on some public forum and becomes a target for the developers to patch against. Also, the more people who are running the bots in game, the less profit you are going to have from selling your items because they're more abundant, so it is better to keep it confidential and just have many accounts farming.
Before the bots were commonplace, there were Chinese "sweatshops" where people were paid scraps to play the games for 20+ hours a day in horrific working conditions. Would hear stories like "man dies from playing MMORPG for 36 hours straight".
Karma of 884 in one day.
Jokes aside, i wish I worked with guys who have so much experience. I'm sure it would be humbling.
Note: You deserve considerable respect and deference for the experience and skill you have no doubt acquired over the years. Also, since there are so few people like you who started programming in those years, you are an unusual and notable person. But don’t let anyone insinuate that it would have been normal for you to have stopped programming by now. It is not.
That doesn't reveal anything other than the state of the industry.
It is a new industry. Many people have been around for most of it or at least large chunks of it. It's impressive when, out of the 60 odd years of a profession existing, one person has been going at it for 57 years of it.
I agree with this with the word "impressive," but with the word "inspirational," I don't think we can paint with such a broad brush.
Consider that many companies have career progression tracks that escalate engineers out of hands-on engineering roles into e.g. architecture roles or managerial roles. Add on top of that the number of people who burn out doing something they love because they find themselves no longer enjoying it now that it's their job.
I can't find hard numbers for or against my hypothesis, but anyone who stays committed to their passion as their line of work for a sustained period of time, even passing through the stages of burnout that might arise, would likely be inspirational to others in the field who might've burned out or feel like they're about to.
That said, your acute awareness of age bias is something I think more of us in tech (especially infosec in my case) need to actively embrace.
Not related to your comment, but there's certainly precedent for this:
"You're so articulate"
I’ll probably still be writing code when I’m 74, because I like to make the machines jump and shout. But as a working pro? Probably not.
Personally, I find it impressive that the OP has managed to stay relevant and active. Hard to do in any field and not just because of ageism.