The latest articles on DEV Community by Brian Duggan (@briand91). https://dev.to/briand91 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F347456%2F54ccb5ca-55af-4aa6-b8bd-63e7268b0d83.png https://dev.to/briand91 en Brian Duggan Thu, 12 Mar 2020 15:58:56 +0000 https://dev.to/briand91/micro-lesson-shiny-object-syndrome-and-the-law-of-the-instrument-49pd https://dev.to/briand91/micro-lesson-shiny-object-syndrome-and-the-law-of-the-instrument-49pd <p>This is my first post, and I don't consider myself the most eloquent writer. So pardon any errors.</p> <p>Recently I have started diving into React Hooks, and as such I have tried to find any and all excuse to introduce them in my code. They're the hot new thing in state management, right? I mean if you're <em>not</em> managing state with hooks......what are you even doing with your life?</p> <p>And I wound up running into increasingly subtle edge-cases that were resolved by me simply removing the hooks and simplifying any logic I needed in a given component.</p> <p>While hooks are nice and have their place, they, like every other hot new function, library, design pattern, language, are not a panacea.</p> <blockquote> <p>"<em>If all you have is a react hook, every problem looks like it can be solved with state management.</em>"</p> </blockquote> <p>P.S. If you're in the Pittsburgh PA area and looking for a job, Idelic is hiring! <a href="https://idelic.com/careers/">https://idelic.com/careers/</a></p> react hooks shiny