🔥The 9th Round of Easy Loan, Earn $40 Reward is in progress❗️ ⏰ Promotion Period: January 15th - Feburary 15th, 2025 👉 Register now and check more details at gate.io/campaigns/358

Ruben Casas 🦊 Using useState and useEffect excessively takes the "ma" out of "idiomatic React"

Some devs think I'm saying you should not use useState() and useEffect() - that's wrong. They're useful hooks, but there's other hooks, patterns, and React 19 APIs that you should know about. Key phrases here: "a lot" and "experienced"

My opinionated alignment chart for tech talk slides

AI coding assistants save you so much time by auto-generating code, leaving you more time to do other things such as fixing extremely hard-to-debug issues caused by the valid but incorrect AI-generated code

This is such a good visual for the "nothing is wrong with just putting stuff in a bunch of useState/useEffect hooks, my app works fine" React developers

did you know that if you stand looking in a mirror and say "finite automaton" 3 times David K 🎹 will appear behind you and refactor your app to use state machines #lifehacks #productivity #javascript

POV you're about to read the worst code of your life

By the way, I'm not saying "rewrite your entire codebase." I'm saying "the cost is lower than you think, and adding to legacy code usually kills velocity." 1. Understand the code as much as possible first 2. Incrementally rewrite, if it would improve velocity

"Mom, can we have explicit state machines?" "No, we have state machines at home" State machines at home:

Many will disagree, but write code as if you're going to switch frameworks/languages in the future You won't, but it'll naturally organize your project in a way that prevents decay and makes it much easier to maintain and update