• ck_@discuss.tchncs.de
    link
    fedilink
    arrow-up
    8
    arrow-down
    1
    ·
    1 year ago

    It’s actually pretty distinct. DevOps refers to the mindset (or philosophy, if you will) of “you build it, you run it”. It boils down to you as a software developer are also responsible for packaging up you masterpiece, pushing it through CI, getting it deployed and making sure it keeps on running smoothly. It is designed to shift responsibilities away from the sysadmin to the developer.

    The problem with this is that it’s not a role or a job title, so recruiters and HR does not know how to work with it. Hence, they invented the DevOps “Role” because it sounds more modern. So in reality its used as a marketing term most of the time. So when someone pitches you a DevOps jobs, this tells you a few things:

    • they don’t know what they are talking about
    • the company behind the offer puts a lot of meaning into titles, which means things will likely be pretty hierarchical even though they claim it won’t be
    • they’ll likely try to pay you less that your worth
    • lysdexic
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Hence, they invented the DevOps “Role” because it sounds more modern.

      Not quite. Basically a DevOps role includes the responsibility of fixing pipelines and be paged in the middle of the night if something bad happens with the app.

      Instead of paying a sysadmin and a developer who don’t talk to each other, you dump all responsibilities onto someone else and at least eliminate the finger-pointing part between sysadmins and developers when something bad happens.