Great article @javinpaul
. Some really good resources here and you did a great job of laying out how deep DevOps tooling goes. I would add that this is only 1/3 of what 'DevOps' IS. Allow me to elaborate.
1/3 Tooling (as you laid out well very well above)
1/3 Culture: removing silos, shift left, leadership buy-in, failure-acceptance culture, and much more
1/3 Automation and decreasing daily toil. With tools comes management, reduce the management to as low as possible. With tools come data, turn that data into actionable information for humans.
Throwing around 'DevOps' as a marketing term for tools and automation does a disservice to the core concept: bringing value to the organization via product ownership; from developer to end-user. No 'walls' that segment teams away from each other. No more 'not my problem' attitudes. No more 'not my job'.
DevOps is more than tools. That's why you do not see many 'Jr. DevOps Engineers'.
That's true and thanks very much for this valuable comment. I know, it's a job which requires a lot of knowledge and experience, both environment, infra, and tools and that's why only experienced developers are migrating but still it's not the easy job and you need to spend quite a time to know what's going on and how to get most of it.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.