Is sysadmin comfy bros?

lots of trannies there

Junior Sysadmin here. I work at medium sized company. Users use Windows mostly but Infrastructure runs on Linux. It's a pretty comfy job. My first since college and after a year I make very good money for eastern europe. I will probably be moving towards dev-opsing in the nearest future.

I've got just an avg bachelors, applied for security jobs and now have higher salary than my colleagues. At least where i live there is an urgent need for security professionals. That said its not really 'comfy' and i feel like security dudes are never warm welcomed by other department since we are looking for their mistakes

Why is Linux trying to sell me courses to give money to niggers and trannies?

I actually quit my sysadmin work after a few years to become a code monkey.
It was waay too boring for me. But I guess it depends on the job details and company really.

I used to be a developer but moving towards sysadmins/DevOps these days. It's pretty nice. You get to write some code but don't have to worry about maintaining it for the next 10 years. You get some pretty fun challenges too and don't really need to specialise in any particular area of technology.

What do I need to be a sysadmin after studying CS? Any courses recommended?

imo don't bother with courses. Teach yourself. Register with some different cloud providers and set various software up. Try out Docker/Kubernetes, get familiar with package managers and the GNU coreutils.

facts. I came into an internship thinking sysadmin was sitting at your computer managing servers through ssh and making scripts that automate your everything. but the boss told me "hey kid new sysadmin is chef and terraform, come learn this instead". and it's innovative and cool and all but not nearly as comfy, in my eyes

Imagine thinking that configuring operating systems is a job or a skill

imagine thinking that sysadmins just configure operating systems

sorry I forgot they plug network cables in too

ignorant amerifat, certainly

Attached: 2018-12-12 13_36_24-Window.png (675x595, 90K)

I'm starting Junior Sysadmin position in January, moving from webdev which I can't stand anymore after a couple of years.

I do realize though that sysadmin isn't a position that allows for a lot of growth, sure in 2 to 4 years I can learn a few skills and reach "Senior" level, but that's it, you reached the ceiling, it will never allow you to grow in the same way a good programmer could (no, webdev doesn't count).

I plan to do it for a few years meanwhile I study Industrial Electronics which is what I actually like.

I hope you don't think that image proves my post wrong

is sysadmin a thing that a college dropout could do
who uh
failed data structures

>>(((Linux Foundation)))
>>Our Classes
>>Our Courses
>>Our Certifications
Fucking corporatists

I mean, maybe, depends on how hard data structures is. Can a college dropout do it? Yes, absolutely. A particularly autistic high school student could do it.

Do sysadmins get treated as IT lackeys

Any technician can do sysadmin, it is retarded to get a college degree to then be a sysadmin.
I'm not saying it is as trivial as some conceited programmers think, but it is certainly much easier than serious programming.

>it is retarded to get a college degree to then be a sysadmin.
beside code monkey what can you do with a degree then?

Depends on the degree.
CS is meant to work with AI, advanced automation, research, etc. Codemonkeying is what losers end up doing, they are working with something they could have learned with a technician's degree like "Programmer Analyst" which would have saved you a lot of money, or at least Software Engineering which would still be far more appropriate.

But certainly a bachelor's degree is complete overkill for IT positions such as sysadmin and the sort, some companies sadly ask it because HR is fucking retarded, but any decent company will not ask you for a college degree for IT.

I mean, I got a job in webdev codemonkeying with just a High School degree, and I suck at it, come the fuck on, when I read about this losers doing CS to get into webdev I can't help it but to laugh.

its a menial job that doesnt require brain

Ιf that's the case I've got it made
>easy job
>good pay
>no need to really do anything other than kill time
Sounds based to me, I can finally start learning about malware analysis and reverse engineering while I'm getting paid to sit around

This
Why put yourself at risk with programming while you can have a nice base as sysadmin and do whatever the fuck you want on top of that?

yeah almost too good to be true
why don't more people do it then if it's just kind of up for grabs with a limited skillset

idk, I'm doing sysadmin and it's not so fun if you're in an open office and have to pretend to be doing things
it's probably a dream job if you have privacy though

Attached: You.jpg (475x437, 51K)

programmers can make their own money, sysadmins are wagecucks

>t.brainlet who never worked in the corporate

No, everybody is pretending to like you because they often need your help.

I'm sure you're very smart for creating computer accounts for the big business people

Done some different stuff over the years like application support, software engineering etc. sysadmin was most joyful of them all.

It depends, it's either slave work or you're some kind of batman that protects the entire company.

Even what you are making fun of now is much much more difficult than you imagine, before automatization.

You just proved you know nothing about the job.

>But certainly a bachelor's degree is complete overkill for IT positions such as sysadmin and the sort
From a technical PoV? Yes, most of the sysadmin trade can be learned at home (building an homelab precisely for that). Problem right now is that even for sysadmin positions, most HR drones will drop your CV on the spot you don't have a CS degree or similar.

>before automatization.
the very fact that the job can be automated (and it can) proves how menial it is

Any job can be automated.

Attached: 1538653370945.png (750x775, 930K)

creative jobs can't

I've got news for you buddy

ampermusic.com/

bbc.co.uk/music/articles/0c3dc8f7-4853-4379-b0d5-62175d33d557

Infosec gets a bad rep because a lot of assholes tend to end up in the infosec department at the bigger companies.

Small list of grievances I've had with infosec at various fortune 500's.

>scan is wrong and detects software not even there any more. Infosec won't listen to anyone because "hurrr durr I have a cert and everyone below me dumb".

>plays shitty games with permissions and won't work with other teams who actually make money for the company. Haphazardly blocking users from job functions

>won't communicate bad news to company or users and instead just turn shit off cause "muh security" but won't tell or explain why

>literally sits 5 days a week in a cubicle and runs a scan. Demands every other team do the rest of the work to patch and remediate.

> won't accept explaination from other IT teams on why users need X or have to have permission Y. Blocks users from stuff, gets their ass chewed out by some one at C level immediately reverts change only after everyone is collectively pissed off at IT.

>fails to build out new hires in a timely manner for some reason no one on infosec can into automation or scripting

>occasioanlly runs a foul of the ADA by blocking a vision impaired software suite requires going two levels above my manager and some one over at HR to explain to the dipshit with a cert what the ADA is and how much money it can cost a company if they fuck it up.

I could go on.

I remember losing all access to the OU cause "muh security" to find out that Infosec was doing all its active directoy monkey work on one generic account with a never changing password. But letting me touch the buckets in AD would be "bad infosec practice".

Demands to patch shit thats doesn't even have a patch yet. Forces a p1 call gets cto involved... and there isn't even a fucking patch yet!

Attached: 1480944243226.jpg (415x476, 28K)

>reddit spacing
didn't read

Attached: 1543652818207.png (868x958, 258K)

Find a closet or a hideaway and put some techshit in there, then you can hide and pretend to be fixing it.

kek

Wait, according to that chart I could be junior or even intermediate sysadmin? How do I get pussy with this knowledge?

>"experiment with lamp" earlier than "editing files, navigating filesystem, using utils"
WUT

Who Terraform here?

>Linux foundation
Evil material from the evil powers.
They're aiming to make Linux proprietary.

Not me. I tried it and it was absolute garbage. It would constantly recreate the resources even if changing the name (which wasn't necessary). It would also fail to apply 90% of the time because some resource failed to delete fast enough.

Yum.

Comfy. A lot of software devs hate you, since you're finding problems with their code. Or closing things that they use. But it pays well. And some companies will pay for certs and going for master's. Mine does. Some expect you to be able to pass a clearance though.

Hmm okay then I'm interested in both sysadmin and security
Maybe I'll start out as sysadmin and later on when i get bored get a Masters in security and try going down that path

Attached: 1544454979721.png (920x933, 513K)

Attached: 1543923000861.jpg (1280x1650, 543K)

AWS, VCP, RHCSA/RHCE, MCSA/MCSE

this. Don't forget your certs. College doesn't give em.

"Security" has 2 parts: business and actual security engineers.

You will likely be in the first one unless you have a major technical background.

Your job will consist of "investigating" support tickets.

No, you're thinking of helpdesk

I'm having a bad time wraping my head around docker. Why would anyone prefer it over simply SSHing into a server and installing whatever software they need/run a bash script that does it all?

Can you be a sysadmin without knowing Linux these days?
What was before Linux in servers anyways?

This LMAO

Bash script can be written any way, hence no standards.

Also docker is an entire environment in itself, not just installing the software on the bare metal.

It allows a bit better coding infrastructure as code, it's basically a bit better than using VMs and installing shit manually.

It allows you to focus on your application itself rather than the software needed, so you would have a single Dockerfile with all the necessary things needed for your application OR you can have multiple Dockerfiles for each "area" of your app, backend, etc. OR you can also separate your environments between development/production based on your infrastructure as code.

TLDR: It is a much better standard of managing your infrastructure and the software underlying it.

Yes you could do everything using bash or just installing shit manually but it's not really good for complex applications.

You can at large corporations, some work on only Windows based environments.

At a medium or small company? probably not.

Eww, tranny OS.

Security is a bullshit industry. Doesn't matter how good you are because your system will be compromised by some MBA boomer who forces you to make insecure decisions or some CFO who gets his frat buddy at Oracle to hook you up with the newest 0dayable shitware at a slightly discounted rate.

I can definitely see some usecases, it's just the "dockerize all the things" trend that I don't, mostly because i don't fully understand Docker. Once you deploy an app running on docker, can you edit its parameters or whatever directly in the machine where it's running or you have to edit the image from the machine where it was deployed and then re-deploy?

ie, the sysadmin cunt at every company that let's hackers in the system because they were sitting around reading reddit instead of working.
Everytime this happens, both the sysadmin and HR should be fired

you'll be paid 33% less than developers. less advancement opportunity.
but there are still plenty of jobs and its easier

>comfy
give up now

retarded zoomer is retarded

Enjoy getting replaced by Docker and Kubernetes. Unless you're aiming to be a tech support monkey.

- touching many individual boxes to do things doesn't scale, especially by hand
- containers are lighter than full VMs
- better for scaling in general when application/services are designed correctly and setup on something like k8s with an appropriate HPA
- slightly better isolation; you don't need one machine doing everything or many VMs doing somethings, you can split it up per service/application into a container
- more abstraction, less worrying about individual details of hosts, VMs, etc

and so on

You can do either. For example, if you want to have a certain network interface or use different networks for different containers that communicate with each other you can do that as well.

There's just a lot more flexibility when setting up your infrastructure as code rather than setting parameters, etc. manually then not having a version control to fall back on.

Is it even worth it to get a degree or would just self learning and getting certs be enough ?