Confessions of a Full Stack DevOp

Post by KaiserPro » Thu, Apr 17, 2014, 8:35 AM UTC

lewaldman wrote: post #23

KaiserPro wrote: post #4

I am a horseshoe crab. I am a sysadmin. I can code, I do code, but I'm a much better sysadmin, mainly because I've been doing it as a dayjob. You want networking? I'll do that. you want multi gigabyte a second storage arrays? I'll do that. You want monitoring? I'll do that. You want me to recompile python 3.3, naaa you can do that. I can, but you'll do better at it

Wow mate, don't get me wrong (I'm a SysAdmin/DevOps guy) but... From where I came and from my background... RPM/DEB packaging is a SysAdmin job. And... In a properly built infrastructure, what is recompile python 3.3 if not just repackage it?

because unless you work in a startup you have to support legacy, which involves recompiling python(or anything else for that matter) because someone previous did something stupid....

Post by billmalarky » Thu, Apr 17, 2014, 4:33 PM UTC

rantanplan wrote: post #25

billmalarky wrote: post #17

Earlier quoted context omitted.

You've met great developers who couldn't deploy code?

You think that deploying code just means "push to master and reload/restart servers"? Even if you think that it entails more stuff, like knowledge about AWS, rackspace APIs, provisioning tools and whatnot, it's not enough. Mostly because in any medium to large company they build tools and processes on top of them. Have fun learning all of that, while you only need to commit your code. Plus, since I've been for many y…

No doubt deployment is not a simple process in many cases, and I have respect for the ops position. But the line I was referring to specifically stated, "I've met great developers who didn't have a clue about how to scale or monitor their software outside of their framework." To me, being completely clueless once you leave your IDE is a pretty strong sign of a "not-great" developer. For instance, how do you know how to write good scalable code if you have no clue how the sausage is being made? Not saying you have to be an expert at the full stack, but you should have an idea of the basics.

Re: Confessions of a Full Stack DevOp

Re: Confessions of a Full Stack DevOp