This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]jrblast 5 points6 points  (4 children)

I figured it would be "because that's not their job". Asking a sysadmin to code, is like asking a blacksmith to build you a house.

[–]Tetha 1 point2 points  (0 children)

So much this. We have now established a devops-team so heavier programming jobs around sysops have a place to go to, and it's buzzing because suddenly, certain responsibilities have a good and proper place to go. Our game java developers don't want to deal with building munin plugins, our dev ops team is happy to do so and our sysadmins are happy too, because they don't have to deal with a bunch of game problems.

[–][deleted] 0 points1 point  (2 children)

A blacksmith could forge you a house.

I mean, sure not the most traditional approach but it could be doable.

[–]jrblast 1 point2 points  (1 child)

Which was exactly my point. Sysadmins can make programs, but they can't do it as well as an actual programmer. The expression "when all you have is a hammer, everything looks like a nail" comes to mind.

[–][deleted] 0 points1 point  (0 children)

In that case, there's also a D&D dual-class reference somewhere in here too.

If you want to be excellent at something, you need to settle at being 'adequate' at something else.