For reference (as per Wikipedia):

Any organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization’s communication structure.

— Melvin E. Conway

Imagine interpreting that as advice on how you should try to design things, lol.

Tbf, I think most of the post is just typical LinkedIn fluff, but I didn’t want to take the poor fellow out of context.

  • MasterBlaster@lemmy.world
    link
    fedilink
    arrow-up
    11
    ·
    1 year ago

    I was thinking it is parody. The whole thing is management consultant speak. But honestly, I can’t tell any more. So much that would have been obvious parody in the 80s and 90s, are in fact serious today. Regardless, software architecture is really not that different from hard engineering. There are designs that work, and designs that don’t, business culture be damned.

    This comes across as more of “fuck you, build it the way we feel it should be built” even though they have no fucking clue of the difference between a singleton and strategy, or SOLID and DRY. It is like a senator telling a Pratt and Whitney engineer the F-35 must be able to take a 90 degree turn at mach 3. Totally fucking ludicrous!

    • barsoap@lemm.ee
      link
      fedilink
      arrow-up
      3
      ·
      1 year ago

      “fuck you, build it the way we feel it should be built”

      Not really sufficient on its own, you have to fit the organisation and communication structure to the code. That even applies to small teams, even to having a single coding partner, heck it even applies to a solo project you have to get the communication between your idiot and genius self right.