Twitter at the speed of parenting
Software patterns and their contexts, a thread:pic.twitter.com/WUKFvyapfi
Show this thread
-
For the same reason, no small company should be using web components. They exist to solve big company organizational problems.
Show this thread
The same patterns apply, whether we’re talking about object-oriented design, service architectures, container orchestration, or refactoring entire systems. Technical contexts are fractal. But the _organizational_ contexts are different at every level of detail.
-
-
My ears have perked up. Is there any reason not to write things in a limited surface area message-passing way? (You know, like microservices without the orchestration, discovery or networking complexity.)
-
Not sure exactly what you’re asking, but levels of abstraction are never free. They create mental overhead to understanding control flow. Hopefully they pay it back in improving findability, extension, and reuse, but tbh in many cases they don’t.
-
See also: the wrong set of small objects is worse than a long procedure. (A
@sandimetz truism.) At least with a list of instructions you can tell what’s happening ¯\_(ツ)_/¯ -
Reasonable to be sure. I'm just always looking at monoliths that seem so conceptually spread out that contexts are just too wide and deep; they often seem woven.
End of conversation
New conversation -
-
-
greath POV. I feel there's a parallel here with microservices (alas, a pattern) applied indiscriminately to smaller projects that cannot sustain them in practice.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.