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.
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.