Developer-roadmap: DevOps part lack of precision

[eagleusb]

Hello there, I'm picky but the DevOps part fails at some point.

1. Cloud > ~Google App Engine~ Google Cloud Platform
2. We probably want to seperate PaaS (Heroku...) and IaaS (AWS, Azure GCP)
3. The Monitoring part lack of Grafana, Kibana and all tools gravitating around ELK stuff
4. By containers you mean only the runtime, which is only one part
5. We can easily add strace, dtrace, systemtap... for system calls debugging in command tools

The list can be long and I don't know how to handle that, can we define a method of suggestion, by categories or something ?

[Davidsoff]

DevOps should also have read "The Phoenix Project" and have internalised "The Three Ways". Right now this roadmap is just a map to becoming an operations person.

Granted having good Ops knowledge is important it is not the key characteristic of a good DevOp

The three ways:

1. The way of flow.
2. The way os feedback.
3. The way of continuous experimentation and learning.

[eagleusb]

Totally agree with that, but even for an operations person this map is simplistic. We can try to add at least the good categories and some tools as example.

[k4ml]

I suggest renaming DevOps to just Ops. Making it separate suggesting it is a distinct field or role while it's more of a culture, which should be embraced by both dev and ops (hence devops).

[kamranahmedse]

There have been changes made to that section which makes this issue outdated. Thank you for reporting though 🙏

[030]

I agree with @k4ml. DevOps is a culture and not a role. @kamranahmedse Could

DevOps Roadmap
Step by step guide for DevOps or any other Operations Role

be changed to:

Ops Roadmap
Step by step guide for an Operations Role

Apart from this, I like the roadmap.