fredericrous.com
Enterprise Architect | Passionate about #NodeJS , #React & #TypeScript
Exploring decentralized tech, OSS, and all things computing š¤
š«š· Paris
š fredericrous.com
92 posts
58 followers
492 following
Regular Contributor
Active Commenter
comment in response to
post
tell us more šš
comment in response to
post
and it even plays on mobile! great job!
comment in response to
post
reasons to do css-in-js are better DX, dynamic theming. and the perf tradeoffs: most css-in-js libs inject styles at runtime, so your css ships with your js, which can impact different perf metrics if not carefully monitored. I think mainly to layout shifting, lcp, tti
comment in response to
post
css-in-js means writing your styles inside your js/ts files, next to your components. there are many ways to do it. Some libs run at runtime (styled-components), others are compile-time. Stylex even gives you TS type safety for styles.
comment in response to
post
Switched to uBlock Lite š
Totally forgot that uBlock was a Manifest V2 extensionā¦ I remember thinking it would disappear back when I built a Manifest V3 extension at Storyful
comment in response to
post
If you ignore your timesheets long enough, they eventually get filled automatically. Learned this from a senior dev when I was a junior! His manager did them for him for years. I donāt think the manager was happy about itā¦ but hey, it worked
comment in response to
post
What if we had an AI bot to handle their questions one by one? š¤
comment in response to
post
yeah! this css animation is totally cool! and creative! I love it!
comment in response to
post
Iād even go as far as volunteering to write the meeting minutes š That way, thereās a 100% chance everyone gets an email with the action items!
comment in response to
post
Just did it. I noticed that āTime Sensitiveā notifications was checked. That must be why I was seeing more notifications from X than expected
comment in response to
post
I guess hiring people who can ace a BFS interview but havenāt touched DDD, load balancers, or streams before is catching up to them. Just being sarcastic here. I donāt know for sure, but I wouldnāt be surprised
comment in response to
post
things take time. Also few influencers stayed on X because they are saying some of their users wonāt leave the platform. I therefore get notifications from X and it keeps me reading/posting there š„²
comment in response to
post
Wonderful tree! You should decorate it with colored wires
comment in response to
post
Fair point! Nice that everything was already set up seamlessly
comment in response to
post
no typos! I do the same, weāre geniuses š risk is for the others
comment in response to
post
My experience was already amazing back in 2019! On top of that, I use Chezmoi and a Brewfile to automate my dev tools setup (mostly command-line tools like bat). Did you automate your dotfiles and dev tools setup too?
comment in response to
post
renegotiate the deadline. Or a bonus š Iām too old to do free extra hours
comment in response to
post
you must have a great vision. I cannot read these pic at all š¤£. But Iāll read the article, thanks for sharing
comment in response to
post
PubSub fits great for what I want to build. Focusing on transactions, I'm working on a CQRS app and looking for event sourcing examples to implement rollback. Mentioned effect/cluster because cluster-workflow includes an event journal, which caught my interest
comment in response to
post
you mean dev, prod and ephemerals? why keep dev then?
comment in response to
post
the same as for any other branch? What would be the rules to merge a feature branch in your usual scenario?
comment in response to
post
This is going change how I write a number of components š². Looks like Iāll be relying on useEffect a lot less now!
comment in response to
post
For French speakers learning to program 20y ago, the only free resource was Le Site du ZĆ©ro. It had tutorials and a forum. Some were great, others average to poor. A lot of people learnt how to write their first lines of code from there ^^
comment in response to
post
Sure, there's noise, but we're in a better place for learning tech now. I remember trying to learn 3D shaders and mapping back in the day. No tutorials, just obscure forums, and you'd better speak English to get help
comment in response to
post
That's funny! š Thanks for doing your part to put an end to star begging!
comment in response to
post
š¤Æ This is amazing! thank you! I can't wait to give it a try
comment in response to
post
I understand the code here: that cache is outside the scope of the component, that @ricky.fm uses the new use hook. But Iām struggling to see the correlation with his first statement. Maybe this could make for a great topic in a good old blog post? It might help clarify things for others too
comment in response to
post
this convention is used by the remix community. I found it easy to work with remix.run/docs/en/main...
comment in response to
post
It's a React Native app. At the moment, React Native feels like weāre primarily building for iOS and Android, with web compatibility as a fortunate side effect
comment in response to
post
Fair point on the 300-char limit! To clarify:
- Firehose: Like AT Protocol's firehose (streaming of messages)
- Entity rollback: Think DDD-style, a level above DBs, embedding multiple DBs. For this, I'm waiting on Maxwellās effect-cluster refactor. Tricky topic!
comment in response to
post
Looks correct. The list of messages gets hidden at the bottom, so you need to scroll down to see it. One solution is to use scrollTo + scrollHeight for a fix. But consider what happens if the user opens the input while scrolling through the list
comment in response to
post
Thank you for the great thread! Is Google working on a WASM orchestrator? Also, are you familiar with Internet Computer? Iād love to hear your thoughts on it
comment in response to
post
Beware: Using WASM in the browser comes with overhead due to messaging between the main JS thread and the WASM module. For simple operations, this cost can outweigh the benefits. I use WASM for tasks like cryptographic operations where performance justifies the trade-off
comment in response to
post
Feels like Angular wants to steal the show from React š Just kidding, of course. React 19 is dropping right around the same time. And yes, I know thereās no comparison between peaches and apples. Just happy to see the web moving forward, congrats
comment in response to
post
Example of negotiation: "Hey, I started refactoring this part! Should only take a few weeks..."
2 months later: "Alright, Iām done!"
ā¦ Just kidding. Or am I?
comment in response to
post
Depends on the project size, bug density, and mood. I aim for balance: fix whatās broken and negotiate with the team or PO if a rewrite feels essentialā¦ at least, thatās what I used to do. These days, I just point at the garbage and tell others to refactor :D
comment in response to
post
For Christmas, Iād like to learn two patterns:
- Build a firehose with @effect-ts.bsky.social for real-time streaming
- Implement transactions with rollback for entities, similar to DB transactions but at an entity level
comment in response to
post
I donāt usually pay for a component library, but I would for a particularly complex component. For example, I once paid for a month of support at @xyflow.com Even though I didnāt have many questions, the rapid responses and access to pro examples saved me a lot of time