This kills the sysadmin

As a Dev: You'd be surprised my dude. A lot of devs have an understanding of the very low level and very high level, but nowhere in between.

Sysadmins spend 10% of their time holding devs hands, giving them an environment to deploy too is a piece of piss. Something like gsuite and office 365/Azure are arguably a bigger threat to your average sysadmin but even then those services still rely on on-site infrastructure like RODCs.

is that what you tell yourself to feel better?

This kills the DevOps :)

Attached: 1 14MfkF7u28UseNos5HMXIg.jpg (1024x512, 80K)

They are technically two different skill areas. You can be proficient in both and its great if everyone were just a little, but many people only know how to write software but no clue how to deploy it reliably. Kubernetes and other adaptive 'cloudy' stuff has been great for defining what sysadmins do in code, but if you don't have sysadmin knowledge you'll probably do something stupid.

There are more people than just developers in a company, do you want your developers troubleshooting wireless access point issues or installing new switches? No, you want your sysadmin doing that stuff

good

It /should/ but in practice the majority of sysadmins and software developers are both severely under-qualified and severely lacking in understanding of the complete picture of how computers work. When you have sysadmins who, any time there's a performance issue, say 'looks like Tomcat is using a lot of ram. Probably a memory leak' because they're too fucking stupid to look at JMX and see that the JVM is only using 10% of the heap, and developers who literally can't figure out how to upgrade their local Tomcat install, trying to move to on-prem Kubernetes takes 10 times longer than it should. If it were up to me we'd have moved to the cloud by now, I'd have been able to set everything up myself, and hook up Spinnaker or GitLab to Kubernetes and have everything idiot proofed by now.

This. Hosting a web application does not require a sysadmin anymore, but operating an office environment does. Get people with a pulse to handle the switches in all the buildings, the thin-clients, the VDI server, active directory, and all the other lights-on stuff that isn't worthy of the SRE team's time.

>Does the average dev really not know how their own OS works?

not saying devs are dumb, but really some of the shell/linux stuff I had to rewrite really made me think. in an ideal world, I don't think they should exist, but at some level someone has to be responsible for something even in the most extremely optimistic case.

lead by example dude, looks like you've identified some serious areas of improvement

but then you get the, "no time/budget" from someone with authority and nothing happens.

I'd consider leaving. Staying in this job means you're at a risk of falling behind on skills that SysDevSecOps™ practitioners are learning at your employer's competitors

How are system/network admins still a thing?

Why do we need a special person to plug cables into switches?

Especially now when there is WiFi everywhere and cables are finally becoming a legacy "technology"?

Anyone tried Lambda?

Yeah we've been using it for years at work. I was a fan seeing as it was a grad job and I knew jack shit about deployment of code, really simplified things for me at first.

Mostly listening to kinesis streams off the back of our cms DB

Be wary that the error handling behaviour changes depending on how it's invoked, whether it's invoked on the back of a stream, asynchronously or synchronously.

There's still enough work in your average company to facilitate a sys admin. Changes in a companies workflow, new software for example will need a sys admin. You could just rely on a consultant but they will cost a lot more, SMB don't need them, they can rely on MSPs now but larger organisations still make good use of a sys admin/internal helpdesk

Devs develop, sysadmins administrate. Come on.

i work in a traditionally retail company. i just got onboard but the 'senior' IT specialist at my company is basically an ex-gas station clerk who knew how to use office 365 somewhat. it's terribly frustrating being a web developer here and my only partner is a guy who only knows how microsoft shit works and hardly knows anything else.

also the dude talks like a fucking hoodlum. he calls everyone 'bro'. his dad is business partners with the executives though so he is the senior 'IT' specialist.

can't wait to do my time here and gtfo it's fucking life draining to work in such an environment.

fun fact: if every sysadmin in the world took a lunch break at the same moment, they'd be coming back to their desks fending off wasteland raiders and packs of mutants.

>also the dude talks like a fucking hoodlum. he calls everyone 'bro'.

fucking toxic masculinity

It's an unfix-able problem, white men should all be either castrated or killed

why so extreme? just make them wear skirts. pants create a pressure on their balls and heat them up excessively, which leads to frustration and agressive, competetive behaviour. this is why boys in skirts are best coders.

come on bro
*hugs*

brogrammers and chadmins, can't win either way

I have identified plenty of areas of improvement, we're sending people to training, I've automated a majority of our deployments, I am in the middle of getting HA set up, I'm containerizing everything, moving us to Kubernetes, and bringing in continuous delivery and theory of constraints centric processes. But it all goes so slowly when nobody else has any clue how to do any of it and I have to help get people up to speed before things can be implemented.

Every shop I go to its the same deal when it comes to delivering these strategic initiatives. It's never just the stated goal; there's years of catching up to do. It's never 'just move to Kubernetes'.

I'm currently doing sysadmin shit at my school's cs department. There are a lot of great people on the dev side that can't really maintain a decent production system. Even Linus admitted that being an OS dev does not necessarily make you a systems bro. Devs are too busy doing meaningful shit. That said, there are a lot of people who go into administration because they can't write decent code to save their life. I constantly encounter dipshits who insist on the superiority of ruby on fails and bundled, pre-configured crap because they're too lazy to fix or properly configure an existing solution. If they're even capable of coding anything, it'll typically be cludgy, unreadable python/ruby scripts doing something that can be accomplished in a few lines of bourne shell. If a CVE comes out for a piece of software that they use, they'll just patiently wait till the patch comes around without considering any mitigations that can be done in the meantime. Devs shouldn't be expected to know how to do an admin's job; admins should know how to do their own fucking job.

Get the fuck out tumblr, none of you fucking rodentbrains can even write fizzbuzz

>my admins are bad therefore all admins are bad
>referencing people working for a fucking school
get out

Sysadmin here, here are some things I do almost every single day working at a 150 employee company:

>help devs and testers understand git
>fix or reimage SBCs (ie raspberry pi)
>reset passwords, make user accounts, manage permissions across various services, etc
>maintain offsite backups and backup system, deploy backups as necessary
>manage ELH stuff
>keep various services up to date
>maintain asterisk service and phones that connect to it
>manage a fleet of 40+ Android phones and the ATT business account they're all on
>workstation maintenance, repairs, updates, etc
>communicate with our three ISPs in case of trouble
>manage firewall configuration including allowed hosts, services like DHCP, DNS, VPN, etc., failover
>maintain physical infrastructure in the building such as backbone fiber, switching, physical servers, ethernet cabling

Explain how devs are gonna do all that shit while also doing their own jobs or how kubernetes solves these problems.

Forgot to mention, I'm also the "helpdesk" people go to when their equipment doesn't work. Guarantee devs aren't gonna do that shit, not even I do and I get paid for it.

>tfw will never finish compsci
>tfw will never become a dev
>tfw will never be more than a sysadmin
>tfw will never make more than 55k

Attached: file.png (540x545, 372K)

>kills the sysadmin
>creates the devops software engineer
Same shit. New title.