In 2018 I want you to stop obsessing over inconsequential things in development. Don’t convert all classes to functional components because some lint rule told you it’s good. Don’t separate “presentational components” until you actually use them twice. Etc.
What if this is bad? It's often during routine maintenance of code that people spot logical bugs and design flaws. This is similar to how it's often preferable to be attentive when munging data. You want opportunities to understand what you're dealing with.
-
-
Automation is anti-exploration.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.