Not sure if you're only ever worked alone, but there's an awful lot of value to teams in being able to collectively review designs before committing to them, wh

Not sure if you're only ever worked alone, but there's an awful lot of value to teams in being able to collectively review designs before committing to them, which you can't do if you have to code everything up just to generate the design. There's also the fact that, in a lot of enterprise and government environments, a design needs to be approved before you can implement it, so you need a way of expressing a design that doesn't require you to implement it first. This isn't approval by managers, but by the customers and owners of the environment you're going to be installing software into. Of course, once you have an implementation, documenting the as-built configuration using automated tools that generate from your actual code and runtime system is the way to go.