One of the trends I've noticed from heavy participation in /r/aws, /r/devops, and /r/programming is how many people spend frustrating hours trying to build their way around a config issue rather than looking at configs. Sometimes all you really need is a one line config change
@nathan What do you think people find some daunting about configs? Unknown format? Size? Screwing up worse? Other?
@kin I think most of the times its the shear number of places where you can modify config.
For a modern workload you have code framework settings, code runtime settings, container/orchestrator settings, cloud provider settings, etc
For a new developer they often get focused on trying to solve problems at the level they know, rather than looking at available configs up and down the stack
@nathan Understood. I seem some of it through the Ops lens i have with customers from the API lifecycle, but also sprawling across it--an OpenAPI / Swagger is basically a massive config for this and people struggle. Thanks for sharing. I am working on enablement efforts as part of my JSON Schema team -- see what I can cook up to assist people.
