How much does your organization's structure interfere with your architecture, on a scale from 1 to Monorepo?
@deadparrot Why would Monorepo be more interference here than a gazillion repos, each belonging to a separate team?
@dtanzer Oh a monorepo is the result, not the interference. But I've come to the conclusion that one side influences the other and vice versa. It's a continuous circle, it only matters what's easier to change.
@deadparrot So, Conways Law? I'm happy that most organizations learned by now that it's not always useful or pragmatic to have each single piece of code in a separate repo with independent ownership, pipeline, documentation, dependency management etc. :D
@saxx Yes, it's always Conway's law :-)
And in the end it's just a tool like anything else, but not always the right one.
@deadparrot I would be very curious about the details that led to this post. 
I consider versioning one of the central challenges in software development. I'm not aware of good any resources which are neither too simple nor too corporate.
So I wonder whether I'm the only one struggling with it or whether nobody has a good answer. 
@achim Ah, the details are just my mood for general shitposting :-)
@deadparrot
Between "legacy protocol" and "just change as little as possible"
@deadparrot interesting phrasing - imho this is a symptom of thinking that IT in general is sort of a parallel world instead of a basis.
If a monorepo does not reflect your organizational structure it's a hindrance, just as independent repos might be a hindrance in organizations that need tight coupling.
So I'd flip the question: how much does a monorepo hinder your organization, from 1 to deathstar
@yoggyd That's brilliant, clearly one side can't function without the other. I like that a lot! On the other hand it seems like software is always easier to than orgs.
@deadparrot ha, yeah it does, doesn't it... stupid hoomans, always being so uncontrollable 
tells you something about rigid processes though, but this is getting philosophical:)