[coconutoctopus]

I'm actually a full stack dev with minimal exposure to what you listed above, ci/cd, docker...I'm also wondering about the opposite. Right now, our small team doesn't have a devops engineer, so I pretty much have to figure out how to do some of the devops stuff. It feels way more straightforward and less stressful than doing full stack work.

[frompdx]

> It feels way more straightforward and less stressful than doing full stack work.

It is when everything works!

Kidding aside, one thing I like about DevOps work is that it doesn't get the same kind of scrutiny that other development work involves. Your manager and product manager can see and interact with a client app, but the infrastructure component is opaque to them unless they have experience in this area. In my experience this helps keep the pressure off of you and allows you to work more autonomously. The downside is that you may not get as much recognition when brownie points are passed out.

[f00_]

worst part is being on-call/responsible any time something goes wrong on prod

[frompdx]

True, this can be awful if your org operates globally. This isn't a big deal in orgs that deal with a single region. However, I will say the worse part is that when things go wrong, you are first to get a call which can be very stressful. I still get anxiety when someone uses the :rotating-light: emoji.

[toomuchtodo]

And not being paid for that time (in most cases).