Re:Salary transparency at Stack Overflow
by toomuchtodo on Wednesday July 27, 2016 @03:20PM
(#12175755)
> that in my experience a highly qualified Ops person will /also/ be a skilled developer, but a highly qualified Developer will /not/ be a skilled Ops person.
I have ~15 years of ops experience, and I'm not a skilled developer. I bill ~$200/hr for infrastructure/AWS architecture/DevOps consulting (when not at devops day job), with limited need to be proficient at software development.
Re:Salary transparency at Stack Overflow
by nasalgoat on Wednesday July 27, 2016 @04:51PM
(#12176429)
Curious where you're getting that hourly without also doing coding.
I'm a terrible programmer but I have 20 years of massive scale op experience.
Re:Salary transparency at Stack Overflow
by toomuchtodo on Thursday July 28, 2016 @12:09AM
(#12178264)
> Curious where you're getting that hourly without also doing coding.
Both startups and enterprises.
> Henry Ford once balked at paying $10,000 to General Electric for work done troubleshooting a generator, and asked for an itemized bill. The engineer who performed the work, Charles Steinmetz, sent this: "Making chalk mark on generator, $1. Knowing where to make mark, $9,999." Ford paid the bill.
I think that I failed to communicate my meaning clearly in that statement, so I will attempt to clarify. What I mean is, that in my experience a highly qualified Ops person will /also/ be a skilled developer, but a highly qualified Developer will /not/ be a skilled Ops person. E.g. based on skill-set alone, highly qualified Ops people bring more skill to the table in union than a highly qualified Developer. Whether that's the skills you value or prioritize as an organization or not is another question entirely.
For the purposes of my salary comparison above I used the same years of experience and skill rating in the calculator for the Site Reliability Engineer and Developer roles. As you say, I would expect a highly qualified Ops person to make more than a "merely skilled" developer. I wasn't really trying to state anything opposite of this.