sarahcodes (@sarocodes) header
sarahcodes (@sarocodes) profile picture

Lead Web Engineer 🕸 Hobbyist Game Dev 👾 Irish 🇮🇪 living in NL 🇳🇱. (they/them, she/her) Opinions my own.

Utrecht, The Netherlands
Joined June 2019
Photo by sarahcodes (@sarocodes)Photo by sarahcodes (@sarocodes)Photo by sarahcodes (@sarocodes)Photo by sarahcodes (@sarocodes)Photo by sarahcodes (@sarocodes)Photo by sarahcodes (@sarocodes)Photo by sarahcodes (@sarocodes)Photo by sarahcodes (@sarocodes)Photo by sarahcodes (@sarocodes)Photo by sarahcodes (@sarocodes)
sarahcodes retweeted
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.
2
2
23
11,023
sarahcodes retweeted
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.
7
4
1
34
18,208
sarahcodes retweeted
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.
20
52
5
550
137,350
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
16
53
8
485
116,621
sarahcodes retweeted
Replying to @pauxdsantamaria
@pauxdsantamaria has such a cool idea with TypeScript Gameified 🔥 I just recently discovered it and have to say so far it's a fun time! Highly recommend if you're bored with todo apps and looking for a novel and fun way to learn TS 🎮 typescriptgamified.com/
1
2
2
227
sarahcodes retweeted
The women you see today in tech - we have made sacrifices to follow our passion and be in this field. Kudos to all of us that have stuck it out and are becoming who we want to be - we have generations looking up to us, we are blazing a path. 🔥
13
33
4
436
19,401
sarahcodes retweeted
Autistics don't "think in patterns". We "think in systems". I'm watching this online course on complex systems and on *emergence* - I was like "but that's how I think". You know - small things stacking up to become big things. Can't believe we don't all think like that 💀
55
348
54
3,684
197,282
The thing I think most people miss about burn out recovery -until they are forced to figure it out for themselves- is that there is no returning to before. The burn out is there to teach you to build a NEW life for yourself. One that is more supportive of who you truly are.
10
123
10
636
32,363
sarahcodes retweeted
Forcing someone to do something “outside their comfort zone” before they are ready is not helpful, it’s harmful. Neurotypicals think doing this “builds character” or whatever, except it doesn’t… 1/5
79
2,606
225
16,847
sarahcodes retweeted
"You don't need JavaScript to learn React or Vue" Well, you don't need running shoes to run, but it fucking helps!
71
155
13
1,308
sarahcodes retweeted
I've been working in React for nearly a decade. But over the years my approach has radically evolved. Classes ➡️ functions Mixins ➡️ hooks prop-types ➡️ TypeScript Custom boilerplate ➡️ create-react-app ➡️ Vite/Next/Remix React state ➡️ Redux ➡️ React-query + context
25
47
525
sarahcodes retweeted
Developer productivity requires balancing two competing desires: 1. Improve process. 2. Finish the current task. It’s often tempting to improve something that’s important, but unrelated to my current task. So, these two desires must be balanced.
4
51
5
314
A clip from Don’t Look Up, and then a real TV interview that just happened
5,492
178,716
22,978
739,540
debugging strategy: verify things people tell you
29
162
21
898
sarahcodes retweeted
This often backfires
35
1,323
150
6,545
I really like React. I think it's a perfectly capable UI rendering library that can interact with my app logic (data, states, transitions, effects, etc.) that I keep *outside* of React as much as I can.
21
41
7
522
sarahcodes retweeted
in any case this expectation that all art must have a clear moral message or lesson is, quite frankly, incredibly limiting. It infantalises audiences and flattens out complexity and nuance.
1
4
2
18
I’m very excited to finally announce that my debut #wlw novel, Truly Wanted, will be released with @boldstrokebooks in October 😍 I can’t wait for you all to meet Sam & Brooke and hopefully love them as much as I do! boldstrokesbooks.com/books/t… #writingcommunity #writeLGBTQ
18
26
4
103
sarahcodes retweeted
Love this framing of the engineering career ladder -- it tracks well with my experience, and reflects the importance (and increasing complexity) of technical communication + leadership.
This Post is from an account that no longer exists. Learn more
1
3
The vocabulary we have around burn out is insufficient. It's often framed as too much work (which is definitely one factor), but I see it also stem from misalignment in terms of strategy or values, lack of recognition, and/or sense of belonging.
59
349
44
2,581