doradoblank

4 ms·

1.
by doradoblank 1y ago
Weird to me when people describe React as overly complex. The fundamentals are very easy to grok. You don't need a the more complex APIs to get going.
2.
by doradoblank 1y ago
How do you handle state that affects multiple components? Like a filter button that affects a list table. In React you just hoist the state up and make both components dependent. If you're managing all state via internal component stat
3.
by doradoblank 1y ago
Web components are neat but they don't solve the problem React solves. React provides a simple mental model for managing client state, which is the one of the main challenges in frontend. It's basically, "re-render everything
4.
by doradoblank 3y ago
NextJS is a batteries-included full-stack framework, Vite is a lot more minimal. If you're just looking to stand up a SPA frontend for your BE, I'd recommend going with Vite, or using NextJS but going full SPA-mode. Doing things i
5.
by doradoblank 3y ago
"The Passenger" by Cormac McCarthy. It's an absolute delight. Nobody's working on his level.
6.
How can you send email from users' email accounts?
1 points by doradoblank 3y ago|5 comments
7.
by doradoblank 3y ago
Have definitely been there. And I’m still working on it, on some level. Here’s what I would’ve liked to tell my younger self. 1. Understand it takes time. There are no shortcuts to intimacy. Come on too strong, whether it’s just friendship
8.
by doradoblank 5y ago
Totally agree. It's just a starting point, and it's not the only model. And agree that it's more helpful for those who are more junior. But I tend to think: prevalence is some measure of efficacy. It exists because it tends t
9.
by doradoblank 5y ago
Scrum is a tool, it all depends how it's used. Kind of bizarre to me that some people think there is no value in planning out work, or thinking about how long it will take, or what will be involved, or prioritizing, or keeping stakehol