> if you're not programming any more, how can you define a modern technical architecture ? Knowing one's limitations is key - I certainly won't get in the way

> if you're not programming any more, how can you define a modern technical architecture ? Knowing one's limitations is key - I certainly won't get in the way of implementers. But functional requirements do drive some architectural decisions and spotting them upstream helps, for example once the conceptual data model and typical query usage are defined, one can decide whether the contractor one sends a purchase order for needs to grok graph databases or relational ones.