4 ms·
I've elsewhere seen described the "Inverse Conway Manoeuvre": make the org fit the emerging architecture. We do this at work. It mostly works, modulo "Distribu
by jacques_chester 9y ago
I've elsewhere seen described the "Inverse Conway Manoeuvre": make the org fit the emerging architecture.
We do this at work. It mostly works, modulo "Distributed Systems Are Hard".
- mpweiher 9y agoI have also done this at work with (what I believe) some success, w/o the distributed systems aspect.
- robotresearcher 9y agoUnless you are a company of one person, you have a distributed system.
- mpweiher 9y agoNo, not really. Now the total system is distributed, but the parts I tried this on weren't. They were Mac and iOS clients with shared code. I moved the architecture from two separate apps that have some shared libs towards a headless app that is basically the same and has two UIs (also with shared code) sitting on top.
- robotresearcher 9y agoSo in what way did you change your org to reflect the software structure, re. the grandparent comment? My reply was about orgs, not your software. Since orgs are made of people, they are distributed systems.
- deleted 9y ago[deleted]
- deleted 9y ago[deleted]
- inopinatus 9y agoOn the other hand I have seen SAP implementations that could be described in the same terms. They are the kind of project that kills the recipient organisation.
- jacques_chester 9y agoSo in the sense of COTS, it might be bad. In the sense of engineering being done inside the org, it seems to work better.
- lomnakkus 9y agoCan you expand on exactly what that means in practical terms? (Please also explain the "modulo" if you can.)