StackOverflow has some data for this.
TL;DR: DevOps makes a bit more than Full Stack.
DevOps: https://stackoverflow.com/jobs/salary/results?l=San+Francisc...
Full Stack: https://stackoverflow.com/jobs/salary/results?l=San+Francisc...
Ask HN: Specializing in DevOps vs. Full Stack Dev
11–13 of 13 posts
Re: Ask HN: Specializing in DevOps vs. Full Stack Dev
#12I actually end up doing a lot of both working in a company with a huge infrastructure but small number of developers.
I would recommend to start solving some of your own problems in the devops space with some REST APIs and frontends :), maybe a self service web UI for developers to create VMs with some of the stack already there and configurable? (Think Heroku)
I have worked in the past 5 years sometimes as 100% React frontend for a medium size project, sometimes as 100% backend developer architecturing effective data structures and data access patterns and sometimes as 100% devops setting the Ci/Cd/Ansible/Docker workflows... Worth noting that in the beginning of my career I worked with digital signal processing in FPGAs and embedded Linux.
I dunno, I feel it is all the same thing. "Specializing" do you mean learning a particular framework? Frameworks change all the time... otherwise, they all run in computers with OSes, CPU, Memory, Disk and I/O.
I would recommend learning the underlying technology and then you can quickly learn anything (literally).
Re: Ask HN: Specializing in DevOps vs. Full Stack Dev
#13It depends on if you are a builder or a tuner. If you enjoy building stuff stay away from DevOps. It feels like endless config changes and fine tuning. If you enjoy tinkering with stuff, DevOps is awesome because there are 1000s of small settings you can play with. If you like control, programming is the way to go because you can pretty much do anything. In DevOps, if developers didn't expose some setting, you are s.…
I wouldn’t say DevOps does not include “building stuff”, but you’re building certain kinds of stuff, like systems to manage CI/CD for projects, deployment environments, promotion of versions, releases, security scans, collecting KPIs on CI/CD (which provide management with more accurate visibility onto the velocity of a project), etc.
Sure, you’re not writing the application, but you’re doing a ton for the work around it to make sure it runs.