this post was submitted on 27 Oct 2023
90 points (95.9% liked)
Programming
17313 readers
233 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 [email protected]
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Speaking from experience, become a system administrator or cyber security engineer and program as a hobby.
I went to school for software engineering then found out near the end that coding all day sucked.
I did the same, sysadmin. Coding for work kills all passion. I still have to do it from time to time but it's not nearly as bad as being a full time programmer.
im actually kinda interested in security and am thinking abt getting a comptia security+ cert whats the day to day been like? same with sysadmin i truly know nothing ab that kind of role
Cybersec is so insanely broad you could do a different job every five years for the rest of your career. Or one job for 20 years like me, despite being easily bored, because every new project is different and there's always new technologies to learn. And you probably have job security for a while yet especially if you are good. For most roles, I doubt AI will replace a decent cybersec person for several years, though it may be a force multiplier.
I haven't done sysadmin in a long time and the field has had more than a few major paradigm shifts: from bare metal to virtual, virtual to container, devops, software defined everything and host as cattle not pets.
Back in the day it was a mix of projects and schedules and emergencies. In other words every day was different and a bit unpredictable. It may be more boring with modern approaches and technologies to significantly improve uptime.
You make sure everything is backed up, up to date and secured, you diagnose hardware issues, to a degree - you diagnose software too.
Best part is that it's engineering, not creative. If the software problem is hard, you open a support ticket with the vendor. If it's hardware, you replace it. There's no solving hard problems of thread concurrency (or whatever feels hard to you) under time pressure.