4 ms·
The author almost seems to apologize for having a django monolith. But it's worth realising that one purpose of code organisation in larger companies is to mir
by sa1 6y ago
The author almost seems to apologize for having a django monolith.
But it's worth realising that one purpose of code organisation in larger companies is to mirror the team organisation. That's a constraint on code that can interfere with the best technical architecture.
You can do better with a monolith in a one-man team!
- efficax 6y agoyou can do better with a monolith on a ten-person team, or a 300 person team. Monoliths have their advantages
- KineticLensman 6y ago> one purpose of code organisation in larger companies is to mirror the team organisation. Sometimes, the organisational structure drives the code structure (Conway's law [0]). I've seen real world consequences of this, where the disconnected system stovepipes in a large organisation reflected the team structure of the organisation's purchasing function. The purchasing teams didn't speak to each other, so neither did the systems they purchased. The systems had separate support contracts, incompatible upgrades, and each one was a wholly distinct integration target, if you were a third party. [0] https://en.wikipedia.org/wiki/Conway%27s_law https://en.wikipedia.org/wiki/Conway%27s_law
- deleted 6y ago[deleted]
- deleted 6y ago[deleted]
- oreally 6y ago> one purpose of code organisation in larger companies is to mirror the team organisation. That's one of the weirdest reasonings I've ever heard. What happens when you have to downsize that team? But yea, shoehorn each individual contributor to say a single microservice out of a hundred and you'll wonder why your software doesn't develop fast - everyone's too tired trying to understand what each abstraction does that is meaningful so they spend less time understanding how the pipeline works and how to integrate into it.