Really interesting piece. I like how it discusses various seemingly disparate issues and ties them together.

> In our codebase, we have hundreds of these jobs, each with their own run_config. If you look at this codebase as a database, you can imagine these jobs being rows in a jobs table, where the fields on each row correspond to the parameters provided to the RunConfig class.

> Wouldn’t it be great to be able to browse all these jobs in a table?

I know the article suggests a database / table, and that could work but I feel like there are a suite of things you'd want on top of that that aren't given for free -- JSON validation, history, libraries with caching, namespaces, etc.

For this exact subproblem, I created www.config.ly .