5 ms·

Came looking for insights, found none. Instead I got platitudes like "sometimes microservices work well, sometimes not" and some copied together cartoon graphs,

• diarrhea 3y ago
  Correct. Even in this thread, it’s just a bag of opinions. Most are elaborate and well articulated, all correct, all wrong nonetheless. No wonder this topic is always such a pile of patchwork. It’s as diverse as developers are.
• dclowd9901 3y ago
  Notably the graphs didn’t make any sense to me. Don’t bugs go up as LOC go up? That’s my intuition at least.
  • vlz 3y ago
    Yup, but who knows, that graph also doesn't even bother with a description on thy y-axis, maybe it is supposed to go from 0 "maximum bugs" (zero code non-buggy) all the way up to "no bugs" (all lines of code bug free). Or maybe the author just wanted something colorful for us to look at.
• IshKebab 3y ago
  I think the core thesis is that "do one thing and do it well" is about small components that are connected together. The classic example is shell pipelines, but they are actually quite shit because they only deal with unstructured data (there's finally some work to fix that in Powershell and Nushell but it took many many years). A better modern example of doing one thing and doing it well is apps that support plugins. ---- I think the whole "do one thing and do it well" is terrible advice. A "thing" is not well defined. It's equivalent to "don't have too many features" which of course leads to "how many is too many" and you're on your own. It's one of those bits of advice like "premature optimisation" that is more often used to excuse thoughtless design than to motivate good design.