this post was submitted on 15 May 2026
27 points (100.0% liked)
Programming
26955 readers
1184 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
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
Don't over do it. As an early career technologist, there is lots to learn at work. Yes, personal projects are great and learning about different things is nice, but look for opportunities to align your interests with work's. It is too easy to burn yourself out. Especially in the current robots-write-all-the-tedious-code-for-you present. If you can learn and accomplish things at the same time at work, that will do wonders for your CV. Your next employer won't really be all that interested in framework X or language Y other than as a baseline to get in the door. Everyone else will know those things, too. What will make you stand out to future employers is the impact of your current work projects and your ability to cogently discuss it. Software is a means to an end.
Take it from someone with 25 years professional experience in a variety of industries, languages, and tech stacks: protect your brain, man. There will always be something new to learn and some kinda project to do. Don't let the FOMO ruin you. I am currently burned out and on sick leave because I ignored this very advice I am giving you.
I hope you rest and recover soon!