We are doing this trip right now. Hard code -> configurable/scriptable/DSL -> Hard code. The nuance I have discovered is you can do the "hard code" in a wide

We are doing this trip right now. Hard code -> configurable/scriptable/DSL -> Hard code. The nuance I have discovered is you can do the "hard code" in a wide variety of ways, some much more amenable to non-developers than others. Our latest stack goes back to hardcoding because someone can edit the source directly in GitHub and have an updated app deployed automatically for evaluation within 2-3 minutes. Another simple compare/merge operation in the web UI to move between environments. No visual studio, no git CLI, nothing. Simply make desired edits in browser, click the green button & check the URL again when the bell dings. Devops wasnt quite this way in 2012. GitHub+Azure have replaced an entire section of my org chart in 2023. The key for us this time around the dial is to separate "nerd" code from "business" code. Not going to be perfect ever but we can get it very close with intent and all of the experience we built up so far. The configurable/scriptable/DSL stuff definitely does work, but once you get to a certain magic # of configuration points, hard code begins to emerge as superior again. Configurable wins in the middle of complexity. Hard code wins at the extremes.