Devs don’t want to do ops

Hamster said:
Well, it's this place where you get to work on inferior office equipment, get no work done, have no control over the aircon and take excessively long lunch breaks. It's a schlep but it gets you out of the house.
Click to expand...
It’s insane how I managed to work 15+ years on a notebook.

The absolute best thing about working at home has been, besides the actual “at home” part, using a high end desktop. Everything being instant is the only way things should be :cool:
 
If you are referring to client facing Ops support, then there is merit in getting the devs to understand the burden and the pressure when things go wrong. When i was in telco billing, it was 24x7. When we specced a feature my support guys actually took part in the definition and design to provide input wrt how to run the app. Otherwise they were flying blind. We designed diagnostics and supportability into it from the start
 
_kabal_ said:
It’s insane how I managed to work 15+ years on a notebook.

The absolute best thing about working at home has been, besides the actual “at home” part, using a high end desktop. Everything being instant is the only way things should be :cool:
Click to expand...
Funny story.

Early on in my career, I couldn't take working on a dual core "hyper threaded" POS laptop. Anyway, I built an m-itx box off carb and popped it under my desk one day at work. I managed to fly under the radar for 2-3 months, until somehow, management became aware.

I was called in to have a discussion about it, and it while the conversation was being had, the issue was more along the lines of pissing off other nancies in the office because they were stuck with their laptops.

Anyways, I agreed to move forwards on my laptop. Maybe 4 months later, I hand in my resignation. The CEO of a multi billion rand company invites me in for a meeting and literally begs me to stay. I will never forget the look on his face after he offers me a (very good deal), and I look him in the eyes and say no, unfortunately, I'm sticking to my decision
 
The amount of stuff a junior has to know these days is crazy. I remember seeing adds a few years ago for junior dev positions. It had the basics: 1 language, 1 framework, a few tools and maybe JS/CSS/HTML. These days you have to know a cloud platform, docker, kube, several frameworks, etc. It's overwhelming and it's leading to average work. We have become handymen.
 
I do this:
"NoOps (no operations) is the concept that an IT environment can become so automated and abstracted from the underlying infrastructure that there is no need for a dedicated team to manage software in-house."
 
Johnatan56 said:
The issue for me is not getting access to stuff, it's not the actual devops. Right now I'm waiting two weeks while security/ops teams discuss whether they can give me a sandbox for some kubernetes stuff I want to set up as a test for an upgrade migration. Not sure why there's a discussion, I need it unless they want some of my tests to cause ~6 expensive other devs sit around and do nothing, it has no data besides the app itself (with no data entries), that's it, but the fact that I'll need an SSL cert as well means I get to go through all the hoops as though a new production ready app is going to be deployed down the road, great.

Devops in smaller companies is generally better, since you're generally already going to have been the person that manages the server anyways, this way it's a bit easier since don't have to host the server itself and only set up pipelines to build/deploy and usually have all the rights already.
Click to expand...
That is corporate/enterprise life sadly, waste more time waiting for someone else to let you work than the actual work would take to do.
I very much believe that smaller companies can adapt and change strats a lot faster as a result of less policy and procedure.
 
Benedict A55h0le said:
I do this:
"NoOps (no operations) is the concept that an IT environment can become so automated and abstracted from the underlying infrastructure that there is no need for a dedicated team to manage software in-house."
Click to expand...
Sounds a bit like the ANC government, they also thought they could just leave stuff and it would take care of itself...
 
Rocket-Boy said:
That is corporate/enterprise life sadly, waste more time waiting for someone else to let you work than the actual work would take to do.
I very much believe that smaller companies can adapt and change strats a lot faster as a result of less policy and procedure.
Click to expand...
I do not believe this, the size of a company has nothing to do with it being responsive or have business agility.
 
Rocket-Boy said:
Sounds a bit like the ANC government, they also thought they could just leave stuff and it would take care of itself...
Click to expand...
You are misunderstanding, this is not leaving stuff to take care of itself. This is simply automation and is what needs to be strived for.
 
It's bad enough having to read and maintain code of the average dev, now you want me to be on standby and debug their buggy code in production as well? :ROFL:
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X