Twitter at the speed of parenting
Software patterns and their contexts, a thread:pic.twitter.com/WUKFvyapfi
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.
-
-
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 threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
This statemenr doesn't make a lot of sense to me. Web components have many use cases. Maybe you mean small companies shouldn't use them instead of what?
-
Big companies need isolated contexts around portions of a page because they have dozens or hundreds of teams that each own little bits of UI, & they all need to do their work without breaking other teams.
-
If you have one team doing all your UI, all those isolation boundaries are unneeded overhead.
-
I get your premise, but the technology behind WC and the pattern of componentization is not bound to the multi-team paradigm. That's a little like saying OOP is overkill if you're doing everything by yourself; just use Pascal.
-
That’s kind of true tbh. A long procedure is better than the wrong set of small objects.
-
Procedures must be small and compact. Easy to read and reuse. That is what WC are all about. You may be a small company but overtime you may have many projects, where you want to reuse code.
-
You can do that in front end code without WC.
-
I still feel what you're really saying is that most UI developers you know are more comfortable with other tools. Those comfortable with web components would still choose them where they find them useful, whether working completely alone or in a megacorp.
End of conversation
New conversation -
-
-
I'm a company of one and live web components.
-
You’re making your life harder than it has to be then. Which as a company of one is totally your choice!
-
Maybe. I find maintenance is much easier. Your milage may vary.
End of conversation
New conversation -
-
-
I once had a discussion like this, it's really hard to explain to people whi hasn't been in both situation, small and large organizations; writing fire and forget code to reach the next milestone and writing code meant to last for years. Thank you for this thread!
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
100% this. It is going to be hard for many people to digest, but, all those additional layers of complexity only make it harder to build faster.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
They exist AFAICT to encapsulate behavior and rendering concerns, providing a more declarative and semantic representation of a UI component. This can bring great value to a project or company of any size.
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.