5 ms·

Separation of concerns is not dependent on having a network layers between your function calls though. You can have a well structured monolith with different in

by zimbatm 11y ago

Separation of concerns is not dependent on having a network layers between your function calls though. You can have a well structured monolith with different inner well separated parts. It's just easier to cheat in code than over the network.

smadge 11y ago
Ultimately separation of concerns is an organizational and social problem, not a technical problem.
- lmm 11y ago
  Technical enforcement beats "best practices" every time. (But you can enforce separation of concerns through a language that lets you do that rather than needing a network connection)
  - coldtea 11y ago
    >Technical enforcement beats "best practices" every time. Not in my experience. People will find a way to beat even the best "technical enforcement" every time. Not necessarily hack it -- just work around it to move the problem elsewhere.
    - lmm 11y ago
      There's no way to stop people working around things. But an automated warning is far more reliable than constant vigilance on the part of the programmer.
      - zimbatm 11y ago
        Even more reliable is to keep your programs small :)
        lmm 11y ago
        Not my experience.