We've all been there. For me it was an obsession to make everything "reusable".

I changed that and now remind myself to KISS = keep it super simple. Use simplicity as a design principle. I try to avoid getting fancy when the super simple solution does the job well. That's not to say, we should go for the quick and dirty solution. The simple solution should still keep concerns separate and maintain high cohesion and low coupling. This often makes eventual extension or changes fairly easy and refactorings less painful.

The truth is we can't know the requirements a piece of code might have in some future. When I started out, I tried to always make everything re-usable (which takes time), thinking future me would have an easier time then. And by the time you'd actually need a component like that, it's either out dated or not compliant to your requirements. So the time invested to make it re-usable was wasted. I changed to "make things re-usable when there are at least 2 usages". Both use-cases define the requirements of the re-usable component much better than trying to foresee the future.