Lambda the Ultimate

Patterns demonstrate limited but effective knowledge reuse. The next step is to move from documentation to automation, using languages, frameworks and tools to automate more of the software life cycle.

We are using UML for documentation, but we are using models based on small, focused, domain specific languages (DSLs) for automation. DSL based tools can help developers define and assemble components, such as web services, generate their implementations using framework completion, and capture metadata used to automate validation, packaging, deployment, configuration management, test generation, defect tracking and many other aspects of the software life cycle. We are using high fidelity DSL based models as first class software development artifacts.

using models based on highly tuned Domain Specific Languages (DSLs) and the Extensible Markup Language (XML) as source artifacts

My question is: with highly dynamic languages like python, which often reads more like pseudocode, and a complementary declarative language, may be a lot can be accomplished without resorting to DSLs? Definitely beats learning a new configuration language for every new tool.

More at: Microsoft .Net architecture.