Twitter at the speed of parenting
Software patterns and their contexts, a thread:pic.twitter.com/WUKFvyapfi
Show this thread
When we talk about software patterns, we spend most of our time discussing the _technical_ contexts they make sense in. Building an API? Use the gateway pattern! Extracting functionality from a monolith? Use the strangler pattern! Etc etc etc.
-
-
In addition to its technical contexts, though, every pattern also has a set of _organizational_ contexts that it makes sense in - and these are usually implicit in our discussions.
Show this thread -
But these organizational contexts are what separate use from overuse, when it comes to patterns. Ever work on a project where it felt like the team used the Gang of Four book like a checklist? That’s a team that misunderstood the appropriate organizational context for patterns.
Show this thread -
Misjudging the appropriate organizational context for a pattern can be a lot more subtle, though. For example - no startup with all the engineers working together ever needs microservices.
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.
Show this thread
End of conversation
New conversation -
-
-
Strangler? Pretty sure that wasn't in GoF. Can't wait to read up on that one.
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.