Okay! Imagine you have a toy robot that your friends keep building and upgrading to make it better. But every time they try to give it to you to play with, something breaks or doesn’t work right. A DevOps engineer is like the super helper who makes sure the robot gets from the builders to you safely and quickly—and that it always works the way it should.
every time they try to give it to you to play with, something breaks or doesn’t work right
In my first job, the developers were so bad at managing memory, and the users so accustomed to the developers giving them whatever they wanted, that we had to make all the devs write batch versions of everything they did.
That way if a user submitted a policy for processing and it was too big to run in a tomcat instance, rather than spending a day investigating how they managed to run themselves out of memory this time, we'd just tell them they had to send that job to batch. It'd go into queue and run on a whole ass IBM z machine.
We do! It's just difficult for programmers to fathom how creatively retarded end-users can be, so the coverage is lacking. That's why we have you guys as translators <3
Meanwhile, "devops engineer".
Goddamn programmers, man. TEST YOUR FUCKING CODE!
I dunno what to tell you man, it worked when I pushed it :D
In my first job, the developers were so bad at managing memory, and the users so accustomed to the developers giving them whatever they wanted, that we had to make all the devs write batch versions of everything they did.
That way if a user submitted a policy for processing and it was too big to run in a tomcat instance, rather than spending a day investigating how they managed to run themselves out of memory this time, we'd just tell them they had to send that job to batch. It'd go into queue and run on a whole ass IBM z machine.
But you'd be out of work if we did that ;)
We do! It's just difficult for programmers to fathom how creatively retarded end-users can be, so the coverage is lacking. That's why we have you guys as translators <3