On a tangent, I think the use of the word "Engineer" in IT job titles is a bit pretentious... I don't think our "profession" is yet rigorous enough to warrant that title...
On the other hand, the dictionary defines the word's etymology as "one who designs or devises" [from scientific principles] and/or "cleverness". I think that applies, in the best of our practitioners... I just wouldn't stack our profession's training/qualifications against that of Physical Engineers, for instance. Nothing wrong with "Systems Administration" in my opinion... That is what I do. I may do it with the principles espoused in the "DevOps" movement, but it doesn't change what I do (job responsibilities), but just how I do it (hopefully for the better.) W. > On May 8, 2014, at 7:13 PM, Michael Johnson <[email protected]> wrote: > > Has anyone here changed their job title (or had it changed) to reflect > the more DevOps culture companies seem to be adopting? I have actually > seen people use DevOps in their job title, but that feels wrong to me. > How do you go from a Senior Systems Administrator to something like > Senior DevOps Engineer? What would a job description for something like > this even be? I have the privilege of being able to influence this > title, but I am having trouble defining it since most SAs and Devs seem > to disagree on what DevOps even is. > > So I thought I'd turn to my colleagues at LOPSA first since I'm sure > many of you have at least thought of this before. > > Head Chef? Master Puppeteer? > > Thanks, > Michael Johnson > _______________________________________________ > Discuss mailing list > [email protected] > https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss > This list provided by the League of Professional System Administrators > http://lopsa.org/ _______________________________________________ Discuss mailing list [email protected] https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss This list provided by the League of Professional System Administrators http://lopsa.org/
