3 ms·
Though it is quite common, I think this is a very bad way to organise a business. It's as if programming were bricklaying, a simple operation to be performed un
by namdnay 8y ago
Though it is quite common, I think this is a very bad way to organise a business. It's as if programming were bricklaying, a simple operation to be performed under instructions from an architect.
That's just not true, the main reason being that if you're not programming any more, how can you define a modern technical architecture? If you don't know the precise technical limitations, how can you negotiate functional specifications?
Engineering is Engineering, whether it's IT systems or bridges
- liotier 8y ago> 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.