I'm an international freshman in college and currently work at the IT Help Desk while also using JavaScript to help design psychology experiments. I've come across an opportunity for a sysadmin position on campus, which would require me to leave my IT job. The role would also extend over the summer. Though I'm planning to stay on campus during the summer, I'm hoping to find a more relevant opportunity that pays a $6k stipend. The sysadmin job offers about $16 per hour, which would total slightly less than $6k overall. I'm looking to become a software engineer, so I want to know if taking the sysadmin job is worth it, if it could help in my future SWE career, and how it compares to the stipend opportunity.
5 Answers
If you're not keen on hard-core sysadmin skills, be cautious. They are pretty different from SWE skills. Consider if you really want to learn all about networking and security before jumping in, as these might not align with your SWE goals.
It really depends on what area of SWE you want to focus on! If you're into security or infrastructure things, then a sysadmin role could actually be super beneficial. It’s all about the experience you’re looking to gain.
Honestly, I think the experience you gain in the sysadmin job will set you apart in the SWE field. You'll learn the ins and outs of network systems, and having that on your resume could increase your marketability when applying for SWE roles later.
Taking the sysadmin job could really give you a solid foundation. Understanding how systems are maintained post-deployment will boost your skills. You’ll learn a different perspective that can help you avoid common pitfalls in software development!
Absolutely! You'll be surprised how much troubleshooting skills you'll build—these are critical in production environments.
For sure! The debugging experience alone makes it worth it, and it'll help you understand what sysadmins hate about certain apps, making you a better programmer.
Honestly, being a sysadmin isn't directly related to software engineering, so it might not be the best path if your goal is strictly SWE. You'll likely focus more on system maintenance rather than coding, which could confuse your skill development. However, you'd gain valuable experience with system design and what environments software runs in, so there's still some learning potential if you're willing to adapt your focus!
That's true! But think about it this way: interacting with sysadmins can teach you what to avoid in software design. You'll get feedback that can help shape your coding skills in the long run.
I disagree a bit. Knowing how to manage systems can make you a better SWE. Understanding the infrastructure can only help when developing software, especially if you're looking into roles like DevOps.
Exactly! Insight from a sysadmin job can help bridge the gap to those fields. It's no joke that developers often work closely with sysadmins.