This is an excellent article. The thing I noted that bears true with my experience: it's an evolution. As you come to understand the business better and better

This is an excellent article. The thing I noted that bears true with my experience: it's an evolution. As you come to understand the business better and better, you naturally evolve through some of the same steps. To me, the steps feel something like imperative->repl->functional->pure functional->microservices->DSLs I think if you keep to your code budgets at each step of this, it works out quite nicely. F# is a great tool for this kind of evolution because it's both multi-paradigm and plugs into a ton of other stuff. Thanks guys! ADD: It would be a mistake to read articles like this and jump into a DSL, in my opinion. I know a lot of guys who read some really cool books out there on things like DDD and want to start there. What's missing in articles and books like this is the backstory. These folks ended up where they were and were able to do what they're doing now because of a ton of learning. Not learning code. The business, the tech, and the customers all learning from one another. I don't see any way that this doesn't take a good bit of time.