this post was submitted on 31 May 2025
693 points (98.9% liked)
Funny
9888 readers
1095 users here now
General rules:
- Be kind.
- All posts must make an attempt to be funny.
- Obey the general sh.itjust.works instance rules.
- No politics or political figures. There are plenty of other politics communities to choose from.
- Don't post anything grotesque or potentially illegal. Examples include pornography, gore, animal cruelty, inappropriate jokes involving kids, etc.
Exceptions may be made at the discretion of the mods.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I think the problem might be how quickly you quit to do it. It takes a good year to train a new person to be productive. If they only get about a year of productivity from you after training you for a year (and a junior level amount of productivity at that), then it's not worth their time and effort to invest in you. If you did it every 5-7 years instead, it would probably go over better. That's long enough to see whole projects through to completion and then just take a break in between.
There's also the issue of how long you take off. If you take off 6 months to a year, it's less likely that new technology comes in and changes everything than if you take off 2 years. Ex: 2 years from today you can expect huge swaths of industries to adopt using AI tools in day-to-day tasks. Another ex: I'm an engineer, not a CS person. I've helped design computer systems, but sophisticated coding isn't the main part of my job. In the last 3ish years I've seen every system I've encountered switch to containerization.