Live data from Hacker News

Ask HN: Why do I exist as a sysadmin?

news.ycombinator.com

11–20 of 72 posts

Re: Ask HN: Why do I exist as a sysadmin?

#11
post #9

"Whenever I attempt to dive into anything that I would consider "development", such as python programming, it's as if my brain completely ceases to function and all of the words and symbols on my screen turn into an incomprehensible alien language. It doesn't matter how long I stare at it or how much I reference the documentation, that alien language never reveals its true meaning to me." For what it's worth, I've be…

Thanks, this is good to know.

Re: Ask HN: Why do I exist as a sysadmin?

#12

What about learning devops. Take your bash skills and apply them to cloud architecture, containers etc. that stuff will be in demand for a few years. Cloud Architect might be something to aim for.

I have been wanting to try out things like AWS and containers and such, but I haven't had the chance yet. I think part of it is that I haven't had the chance in a work setting to check those things out. We have thousands of physical machines and on-prem VMs. Sometimes I feel like we're kind of "old-world".

Re: Ask HN: Why do I exist as a sysadmin?

#13
You need to write code so that your brain can assimilate this alien language and you'll be able to "think in code".

Coding is difficult, don't let anyone tell you otherwise. It's completely normal to struggle. How long did it take you to learn to read and write English properly? 15-20 years?

Re: Ask HN: Why do I exist as a sysadmin?

#14

You are not alone. I'd guess at least over 50% of folks here would have gone through a similar phase at some point in their lives (learning block wise). Based on my experience, especially over the past couple of years, I've realised that even if I can power through some of the subjects/topics which I find arcane (e.g. linear algebra, tensor calculus), I quickly lose what I've learnt if I don't get to apply the learni…

Thanks

I think that some of my issues possibly stem from a combination of my previous job being a hostile work environment as well as repeatedly being told by other coworkers (and even a former manager) that: "The work that I was doing wasn't valuable."

I still haven't come to terms with it I think.

Re: Ask HN: Why do I exist as a sysadmin?

#16

First off, I think you should give yourself more credit as what you do has importance and you are valued. > "Be a developer, or get out of the tech industry." I don't agree with this. There are plenty of jobs in operations that require the skills you have (e.g. standing up servers and automating the heck out of things) Writing code and creating software was one of the few things that really clicked for me, so I can't…

I do enjoy automating infrastructure. I guess I feel somewhat obligated to dive into the development side due to the industry trends and the constant "Anyone can code", "Coding bootcamps", and such.

Re: Ask HN: Why do I exist as a sysadmin?

#17

First off, I think you should give yourself more credit as what you do has importance and you are valued. > "Be a developer, or get out of the tech industry." I don't agree with this. There are plenty of jobs in operations that require the skills you have (e.g. standing up servers and automating the heck out of things) Writing code and creating software was one of the few things that really clicked for me, so I can't…

I do enjoy automating infrastructure. I guess I feel somewhat obligated to dive into the development side due to the industry trends and the constant "Anyone can code", "Coding bootcamps", and such.

[deleted]

Re: Ask HN: Why do I exist as a sysadmin?

#18
post #3

Okay, first off, being a sysadmin or an ops person is important! You are the first line of defense, and many times, companies just need eyes on systems (all the time). It's your ability to analyze a problem that makes you useful. There are ALWAYS boring repetitive service tasks that aren't rewarded but someone needs to do (this is true for devs too). Most of this probably doesn't seem hard or new to you, but I just w…

"Okay, first off, being a sysadmin or an ops person is important!"

This is the first time that I have heard or read anyone say this in years. Thanks

Re: Ask HN: Why do I exist as a sysadmin?

#19
post #7
post #2

Why try so hard to learn something for which you have no aptitude, when you have other valuable skills? A 5 foot 100 pound guy shouldn’t be trying to learn football at the pro level no matter how high the NFL salaries are. Focus on what you’re good at. There will still be sysadmins by the time you are dead. Get better at your skill set so that you’ll be one of the ones standing.

Its still valuable for a sysadmins to have some ability to program/script, if only to improve his own utility and sanity (automating out trivial/mindless things); however, its not clear to me why sysadmins seem to often have trouble breaking into programming — afaict, they’re extremely similar in practice. Particularly when you accept that most of software engineering is just composing libraries, while system adminis…

I'm not sure why it's as difficult as it is for me. I'm sure there are people for whom it's not as much of a herculean task.

Re: Ask HN: Why do I exist as a sysadmin?

#20
I was a sysadmin and moved to software development. A big part of the difference is mindset. When I used to work with sysadmins often solutions to problems are "google for a while and then call the vendor". You need to get out of that mindset and become more self reliant. That machine you are using was built by humans, that language was designed by humans and you are likely attempting to solve a problem that isn't dramatically different than problems solved by tens to hundreds of thousands of other humans. You can do it.

Without perseverance and mental toughness it's going to be an uphill climb to become a programmer.

Post reply on HN