4 ms·

I’ve had similar experiences as the author, so I’ve started to “overbuy/overprovision” at the store for my projects. If I end up not needing a part, I can retu

• recursive 2y ago
  > If I end up not needing a part, I can return it. If I do, I saved myself a trip. Returning it also cost you a trip.
  • genewitch 2y ago
    Nah. This is fallacious. The return isn't time sensitive (within reason, usually 14-30 days most places here) whereas "I need pipe dope or we can't shower" is time sensitive.
• Pxtl 2y ago
  There is, but it's awful: The "just use the giant library/framework to solve the small problem" approach. Like, I need to store a value or two for this local filesystem-oriented application. Not a lot, just like a "time since last check". YAGNI solution: just dump json to a file. Frameworky solution: Sqlite. You'll eventually need more, and Sqlite is not significantly harder than dumping json to a file, although it feels heavier. Like starting up a small web-project by pulling in webpack and react. If you don't pull in the frameworks ASAP, eventually you'll accidentally find yourself NIHing yourself into Greenspun's Rule. https://en.wikipedia.org/wiki/Greenspun%27s_tenth_rule https://en.wikipedia.org/wiki/Greenspun%27s_tenth_rule