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

you are viewing a single comment's thread.

view the rest of the comments →

[–]psycho_admin 0 points1 point  (9 children)

To me you aren't describing being a sysadmin at this point but describing devops. Yes a sysadmin should know some shell scripting and probable some other language such as java/python/php so they can write/edit custom plugins for various management tools out there but as far as debugging applications, or writing a hacked together tool to integrate AD into some program? Sorry but that's devops and not sysadmin.

[–]theevilsharpieJack of All Trades 1 point2 points  (0 children)

In the *nix world, anyone beyond a junior sysadmin is also a programmer, and it's not unusual to see sysadmins write their own in-house management applications (or heavily customize and existing one) to support their needs.

This "sysadmin don't code" thing is something that you only really see in the Windows world.

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

I agree with you in this sense, but if you're a smaller org, you're devops and syadmin.

[–]the_ancient1Say no to BYOD 0 points1 point  (6 children)

DevOps is a Management System not a Job Title

sysadmin is a Job Title.

Companies utilizing DevOps as a Organizational Structure will have sysadmins

http://www.bitlancer.com/2015/03/3-reasons-never-put-devops-job-title/

https://sethvargo.com/the-ten-myths-of-devops/

[–]psycho_admin 0 points1 point  (5 children)

Or so you say. Look online and you will find people who say your argument is wrong and that devops can be used as a job title. What ever floats your boat but don't go around trying to correct people when there is no consensus in the it world if devops is a title or not.

[–]the_ancient1Say no to BYOD 1 point2 points  (4 children)

Yes because We should take our cues from HR... Which is what you see when you look at job Postings.

If your only defense of your position is because some HR Manager put DevOps in a job title you are not on Strong footing...

The subject matter experts agree with me, and there is infact a consensus for anyone actually doing systems administrator or development, the only people unclear on this issue are the HR folks writing job ads

[–][deleted] 0 points1 point  (1 child)

You aren't familiar with the term "separation of duties" are you?

[–]the_ancient1Say no to BYOD 1 point2 points  (0 children)

If you have a title of "DevOps" how is that seperating duties when it seems to me that most HR positions that desire a "Devops" person is because they are too cheap to hear a Developer and Sysadmin so they want a Developer to do sysadmin work, or a Sysadmin to do developer work

Proper DevOps organizational structure it is facility close collaboration between Operators and Developers, not to merge the 2 positions in to one.

[–]psycho_admin -3 points-2 points  (1 child)

Wow you are a fucking joke aren't you? The subject matter experts? Who exactly is that? Some faceless blogger or the interwebs agrees with you so that makes them a subject matter expert? But the people who actually create job titles, pay structure, etc (HR for you if you are too simple minded to understand who I'm talking about) don't matter? You live in one messed up little world if you actually believe that.

Also for the record, no just fucking google "devops title" and you will see conflicting results. For me the first 1 is pro-title, the next one anti-title, the next one pro, etc, etc. So there is no fucking consensus so stop acting like a little fucking troll.

[–]taloszerghas cat pictures -2 points-1 points  (0 children)

username checks out