3 ms·
The problem this solves is having different teams in the same company perfectly happily developing away on their own stacks when a random business requirement n
by regularfry 7y ago
The problem this solves is having different teams in the same company perfectly happily developing away on their own stacks when a random business requirement needs that they get their components in the same browser window such that neither team is tied to the other's deployment cadence.
- JMTQp8lwXL 7y agoHaving worked at multiple engineering organizations, I could see how some people might question the value of this. For example, A big N company I worked at went all in on React. Top down, no ifs-ands-or-buts about it. I'm biased and like React, so I didn't mind the decision. Today, I'm in an engineering organization where we have teams using React, Vue, and Angular, with no foreseeable convergence on one. Each team feels most productive in its preferred stack. A solution like this allows us to at least ship our code together, instead of having everyone maintain CI/CD on top of their application code. It buys us additional developer productivity. We don't need to be duplicating deployment pipelines.