@kyleshevlin They are really stretching here. At home I can walk my dog multiple times during the day, I can take a break to stretch and do some yoga, I can do some VR at lunch to workout a bit…I sit more commuting and at the office 🙄
Refactoring is rarely “necessary” or “urgent”.
Yet refactoring is important because code is read often, and patterns proliferate.
If we only change code when we “must”, then anti-patterns and hacks proliferate.
So I try to improve the code I’m working with a little each day.
That said, module federation is a tradeoff. It provides a lot of team autonomy, but this autonomy complicates standardization, code sharing, performance optimization, and cross-team changes.
So, I actually prefer a cross-team monolith and a monorepo if the teams can agree to it and collaborate as needed.
Doing so fosters continuous integration between teams and makes cross-team changes easy to do in one PR.
To clarify, Module Federation is just one way for multiple teams to collaborate.
A few other options:
1. A cross-team monorepo
2. Separate teams contribute npm packages that the "shell" consumes
3. Completely separate apps in separate repos and on separate domains that share common code via npm packages, and link between one another.
The advantage of MF is, the shell provides a cohesive cross-cutting experience, but each team can still deploy their "slice" of the app in isolation.
Problem: Your web app is too big for one team to build.
Solution: Use Module Federation (MF) to compose apps.
Here's how it works:
1. One team builds the "shell" (the parent app). It handles global stuff (the header, footer, auth, nav etc).
2. All other teams build remotes (child apps). Each remote is published to a unique URL.
3. The shell loads each remote at their deployed URL. So each remote can be deployed in isolation.
but I don’t think web developers are going anywhere anytime soon. Will we have to adapt to new tools to keep up? For sure? But will be eliminated…not just yet ⚡️
The thing about building complex web apps is there is no one size fits all solution, it totally depends on the needs and the business context and what you care about, is it e-commerce, data insights, ordering system…the list goes on…! I’m really impressed with AI…
@kevinmeinhardt@housecor Yeah this 👆🏻 I don’t think it’s necessarily misuse of context but more poor design that got perpetuated with the popularity of SPAs
Next week I start a new job where I'll be working with Vue.js for the first time. I've really enjoyed primarily working with React for the last six years but I'm excited to learn something new and explore a new eco system 🤩 Tell me what you love about Vue 👀
1. Brands matter when you have hypersensitive taste buds.
2. It’s better to eat “junk”, “unhealthy” or “not nutritious” food than no food at all.
3. Sensory sensitivities should be respected.
4. It’s ok to not eat foods that you find triggering for any reason, big or “small”.
@zachcodes This is not the moment you know you’re a senior js dev. But if you did read this tweet and then roll your eyes and shake your head then you might be a senior js dev 🤷🏻♀️
It took me a long time to understand the value of React. Here are a few things that React nailed, and it is worth learning from.
- Components are functions
- Simplicity of JSX
- Composability of hooks.
- Explicitly not solving some things.
1/5