@IgorMinar 👏we have a web component library coming from a CDN. MFEs use our angular library that wraps the web components (cva etc). We fate share the web components, but can pin MFEs to a previous web component distribution if an issue is introduced. Works 👌but a little homegrown.
I used to be serious about removing obsolete code & processes. After seeing the effect of decades of build-up, I'm now becoming absolutely fanatical about it.
Combine the new JavaScript features “nullish coalescing” with “optional chaining” and a ternary to make your code extra modern and abstract. Your PRs will be unstoppable come review time.
When to apply “if it hurts, do it more”:
When the pain grows exponentially with the time between actions.
- @martinfowler
Deploys, merges — the more changes conflated, the greater the pain. So do it more.
If you don’t own your part of the customer experience, it’s pretty hard to create an autonomous customer-focused delivery team. Continuing to have dedicated front end teams is all too common for “microservice” organisations, and misses so much of the point of a ms architecture
@martinfowler It starts out as dogs and cats, until the business wants a dog with 2 heads and a cat with 5 legs. This leads to degraded OO constructs and at worst the YoYo antipattern when you try to ‘make it work’. It is still taught as the defacto rather than something deeper in the toolbox.