There used to be the idea of the "30-year old programmer retirement" theory.

This is because the working environment for programmers was poor (long hours of overtime and working on holidays was the default).

In addition, programming technology is advancing rapidly and technology is rapidly becoming obsolete, and new programming languages are popping up one after another, forcing them to keep learning new technologies.

I think "always learning" is the same in other industries, but in the world of programmers, I think the trend is more pronounced.

-----

According to the "programmer at 30" theory, I should have retired as a programmer a long time ago, but the reason I continue to do so is

"The feeling of pleasure when the program works as I expect"

I believe that.

As far as I know, I don't know a programmer under 30 years old -- well, my connections are smaller than the hole in the needle, so my opinion is not so reliable, though.

-----

I think the reason why the "30-year old programmer retirement age" theory was disqualified, is the same reason why the "30-year old gamer retirement age" theory does not work.

Game is that technology is advancing rapidly, obsolescence is significant. and new games are coming one after another, they must constantly learn the rules of the new games.

To begin with, gamers don't retire from gaming at any age, do they?

As far as I know, I don't know of anyone who has stopped playing games and switched to haiku, calligraphy, or karaoke! -- well, my connections are smaller than the hole in the needle, so my opinion is not so reliable, though.

-----

After all, "It is important to listen to the theory that is whispered in half"