Consider new sections that are not tools

[odewahn]

This guide is mostly focused on tools and technical practices, but there are a lot of aspects that go to business practices. Should there be a section for this?

For example, here are a few ideas:

• [ ] Building a DevOps culture
• [ ] Design and UX
• [ ] Non-Functional requirements is the competitive advantage (per @ragsns)

There are probably many, many others.

[dethkultur]

First, this is a cool project. I like how you've organized it and split the subject areas.

Design and UX could be getting into a minefield, if for no other reason that new approaches pop up with very high frequency, leaving a feeling that anything previous is outdated immediately if you know what I mean. I do think A/B testing should be included though as a seperate section. It is a best practice everywhere, and developers are always on the lookout for new ways to implement and measure A/B tests.

Also, I think this section should probably be split into two - infrastructure monitoring,for which there are many canned solutions (including most of those listed) and application -specific monitoring where devs need to define their own tracking points custom to the product or workflow they are working on. One takes much more work than the other.