@tannerlinsley The matter is very simple.
Types exist no matter what.
You can put them:
- in your code
- in your mind
I let you guess which one is more reliable
🛠️ git-delete-merged-branches
👉🏻 A command-line tool for keeping repositories clean.
👉🏻 It supports deletion of both local and remote branches and workflows with multiple release branches.
https://t.co/Wa8vImOaqI
Senior engineers/lead developers: How the hell do you context switch between reviewing multiple PRs, everything else that comes with your job and then also working on complex projects yourself?
Gonna be honest, React devs: if your app logic is super simple and only requires fetching + displaying data (CRUD), the only state management you really need is React Query + *maybe* useState.
Consider state management libraries when the logic gets more exciting than that.
Why I enjoy React: I can use the parts I like, and replace the rest.
Don’t like useEffect or useState? No problem. Use third party state (react-query, Jotai, XState, Redux, etc).
Lots of stuff in React is optional. And the ecosystem for alternatives is huge.
#react
@Mokkapps@m4nl5r One IDE to rule them all.. for me it's the key map I am used to, block selection and the refactoring features that I do not want to miss.. I also like that it has everything integrated, e.g. a database client. And I admit: switching is hard when you are used to it for years..