Sai Hari

@kai_h @thorstenball I’m not even sure how to begin to rationalize this 💀

@thorstenball I had one user who had _all_ of their email folders as subfolders in their Trash. I don't know how he started down this hellish path, but after an upgrade the email client decided to delete all items in the Trash older than 30 days. Fun times. Somehow it was my fault?

Few weeks ago, while adding buffer restoration to Zed, I came across this comment. I've been thinking about it every day and every day the same thought pops into my head. Why... why don't you save the file?

@mattpocockuk Yo this is cool. Didn’t know you could make a type that accepts any string but also a list of defined strings for autocomplete support. There’s a few times this would have been really helpful!

"it's unreadable" "a maintenance nightmare" "please don't do this" Your complex types don't need to be complex to use. Let me show you 🧵

@thecoockoo @DavidKPiano Having 1 variable represent multiple states is a great idea and makes things more manageable. I do this sometimes when I need to conditionally render things as well. For example, if I have multiple modals on a page, their state is represented by 1 variable with different types.

@DavidKPiano I'd say merging 3 states into one and using async/await makes useEffect version more compelling

Okay, listen. If you're going to fetch in useEffect(...), you should at least make sure that you're handling: - Loading states - Error handling (rejections & HTTP error codes) - Race conditions & cancellation This isn't over-engineering. It's the minimum code to prevent bugs.

@wesbos This is really cool. Will make it easier to run basic scripts without having to install something else!

Yessssss! Node just shipped the ability to run TypeScript files directly!

@levelsio @pubity That’s awesome! Just saw Luggage Losers get hunted by someone else on Product Hunt too, so definitely can see it get picked up.

A massive Instagram account called @pubity with 38 million followers featured luggagelosers.com today 😊 Until now it was kinda stuck going viral only in India (I think cause of Air India losing so much luggage) only, but now slowly moving into the English-speaking world Will be interesting if hits American news next Thx @littleasaf for telling me and no I didnt ask anyone to feature it, it's all organic

@danestves @kentcdodds This is cool! I’ve messed with Clerk a little bit, but didn’t realize you could do this.

@kentcdodds We do that :) we use Clerk for Auth but everything that happens on the app is handled with our database, we just use them to know if the user is logged

Do not drop your users table or offload user data to a third party. Just don't do it. You can use a third party for auth if you want, but for goodness sake, own your user data.

@flyosity @kentcdodds Yeah this is my impression as well. Something going wrong in your database vs other parts of your app can be a bit more stressful I imagine, so handing off the responsibility can be enticing.

@kentcdodds I think it's a symptom of newer developers actually not understanding databases at all so the idea of actually storing their own data is scary But for everybody else, NOT storing our own user data is the scary part

@SaidAitmbarek @codesandbox Awesome! Thanks @SaidAitmbarek. And yeah, I submitted it on MicroLaunch the other day! It should be in the queue!

@TheSSHGuy @codesandbox let's go kempo, upvoted, feel free to rank it on microlaunch.net too if it helps👍

Hey guys, I just launched Kempo on @ProductHunt! It's an app that lets you build customized code playgrounds powered by @codesandbox's Sandpack package. You can check it out here: producthunt.com/posts/kempo

@codesandbox Thank you for the shoutout @codesandbox team!

Today’s community spotlight goes to… Kempo: a tool to build your code playgrounds using Sandpack 🌟 Kudos to @TheSSHGuy for making it even easier to display live-running code examples, especially in content platforms like Hashnode. Try it out ➡️ kempo.io

@michael_kove @t3dotgg Agreed! Usually, the less nested the code the better.

@t3dotgg I don't understand why so many developers hate early returns. They will nest if-else's, write elaborate switch statements... brah, just exit. Really.

I swear 90% of the ternary operators I see would have been more readable as an early return

@codesandbox's Sandpack package has a lot to offer that you may not know about. If you're interested, I wrote about how to get the most out of Sandpack's Preview component here: hashnode.com/post/clx920dw1… #ReactJS #WebDev #JavaScript

@codesandbox's Sandpack package is 🔥. It's a great way to introduce customized code playgrounds in your blog or documentation. If you're interested, I wrote about how it works and how to use it here: blog.thesshguy.com/sandpack

happy holidays! ✨ congrats to all 282 contributors & special thanks to 👑 @rishi_raj_jain_ @n3o773 @rjacksonm1 @TheSSHGuy @ayewo_ @kafLamed @just_moh_it shoutout to the awesome tech we use everyday 💻 @vercel @supabase @DrizzleORM @shadcn @trpcio @t3dotgg @triggerdotdev

✨ @triggerdotdev contributors shown @rishi_raj_jain_ @chigalakingsley @kafLamed @TheSSHGuy

💡 React Rendering Tip When mapping data to JSX, put your key on the top-level element. React won't search through the child components for the key, which means nested keys won't impact the rendering logic. #reactjs #javascript #typescript #webdevelopment

💪 Remember the React JSX Rule — most attributes use camelCase Variable names can't have dashes or be reserved keywords, so to make destructuring easier, JSX attributes are renamed → font-weight turns into fontWeight → class changes into className → tabindex becomes tabIndex

💡 React Rendering Tip Make sure you use stable keys by default for your React components. Using keys that change every time a component re-renders is inefficient. It forces React to destroy and recreate the component instead of updating it. #reactjs #webdevelopment

⚡️ React Rendering Tip If you want to conditionally render JSX, an if/else statement may not always be effective. You can't nest them in curly brackets because they can't be used as values. Instead, you can solve this by using a ternary operator: #reactjs #webdev