This is pretty much how I sum up what you'd have to be to be "a devops engineer": an actually-full-stack developer with a strong facility for communication and for process.
Such folks are hard to find. I only know a few, out of the dozens of folks I've worked with.
While I have some deep knowledge in a few areas, most of the work I do has a lot more to do with researching tools, tracing down problems, and figuring out solutions that do not always appear on Google or StackOverflow.
That mindset has also served me well when I write backend code.
Science: because a scientific protocol is to be used when making and testing code, to understand every detail, and because it's based on logic
Art: because code should first be written for another human (or you in 6 months) to read and understand, that it works or not is secondary,
Sports: because you need everyday to be in the retrospective of your past performance and try to improve it
Completely false. A full-stack developer applies JavaScript frameworks to create websites. A DevOps engineer applies development methods to infrastructure i.e. infrastructure-as-code. Totally different both skillset and mindset.
The idea that a "full stack developer" is "hurr, JavaScript" but that devops engineers are somehow different is...questionable. I've shipped mobile apps, web apps, backend APIs, and build and operate computing infrastructure at scale in cloud and on-premises environments, while having also had success at the strategic level with regards to the development of and the pursuit of business requirements and objectives.
Write code to tell computers to do stuff. That's all any of it is. The elaboration of the details is important in the small but not important in the large.
I think it's more of a criticism on the term "full-stack" for someone who works on a backend and touches front-end every now and then.
I think everyone is in agreement that what we call "dev0ps" devs and "full-stack" devs have completely different skill sets and mindsets but if I had to attribute "full-stack" to either of these it would be a "dev-ops" dev. (theoretically, real life is messy)
I could say a real-full-stack should actually include EE, chip design, compiler design, kernel hacking, model checking, machine learning, virtual reality, power supply design, and 20 years of experience in Rust.
Or anything, really.
A solution can be technically fantastic, and yet people may not adopt it for one reason or another. You have to get buy-in from people.
I recently interviewed at a place where they vaguely know they needed devops but there wasn’t sufficient buy-in. I made the mistake of taking the interviews at face value. I should have been treating it as consultation from the get-go, drawing out any issues they might have (by starting with pain points), coming up with solutions. I didn’t realize I can be applying the same skills I have while working to at the very earliest stages.
If I were to build a consultation firm, I would sell organizations on the human interaction (because that is easier for people-managers to grasp; it is what they fo for their jobs). However, if I were hiring someone within my hypothetical consultation firm to do this kind of work, I would look at their problem solving mindset and people skills, at whatever experience level they are at.
*And it seems reading that Small Farmer Journal article about how to get started as a farmer with no money, real farmers have to problem solve too.
Why do you say this? This only deflates the meaning of the word impediment. To me it would only create ambiguity when we start using the word impediment for things that are not impediments to the common goal. How would you differ between those?
A: If yes, it is an impediment.
You say nothing to negate the assertion that the parents statements impede the organisation.
A sort of extension of the Lean System where workers from different areas share a common goal of delivering value to the final customer (in production), the same card may require a backend dev, frontend dev, and an ops to share the goal to take this card from idea to production, and then monitoring how it behaves in production.
For people who have not read the same books, "DevOps" mean things like "applying dev method in the operation field" ie. with ansible and the likes, coding the infra. After all, that's what that word seems to mean at first glance.
This reminds me of the term full-stack, some people consider it's just about being good at both frontend and backend, in my opinion a good full-stack is also a good networking engineer as well as good at customer acquisition.
For best ROI:
- integration must be automated and continuous
- delivery must be automated and continuous
- tech debt includes untested code and being late in dependency versions
- the above should be treated as impediments
The purpose of "DevOps" being to deliver faster from idea to production, it does necessarily include a toolchain of CI/CD/IaaS & monitoring tools. From this "DevOps toolchain", taylorists opened positions for developers that can maintain it around a software, they called that position "DevOps", which explains how we got there on having different meanings for the same word.
I highly recommend "Continuous Delivery & DevOps: QuickStart" by Paul Swartout for a first quick read on the matter.