3 ms·
Quite often I'm incorporating a new library into my source. Every new library involves a choice: do I just spend 15 minutes on the Quick Start guide (i.e. "copy
by sgustard 2y ago
Quite often I'm incorporating a new library into my source. Every new library involves a choice: do I just spend 15 minutes on the Quick Start guide (i.e. "copy-paste"), or a day reading detailed docs, or a week investigating the complete source code? All of those are tradeoffs between understanding and time to market. LLMs are another tool to help navigate that tradeoff, and for me they continue to improve as I get better at asking the right questions.
- LtWorf 2y agoIf you spend less than 15 minutes before even deciding which library to include and if include it at all. You're probably doing it wrong.
- smikhanov 2y agoNo, that person is doing it right. That’s 15 minutes of your life you’ll never get back; no library is worth it.
- faizshah 2y agoIf your goal is “ship it” then you might be right. If your goal is “ship it, and don’t break anything else, and don’t cause any security issues in the future and don’t rot the codebase, and be able to explain why you did it that way and why you didn’t use X” then you’re probably wrong.
- LtWorf 2y agoThat applies to working in general.
- LtWorf 2y agoThe past weeks at work have been spent replacing libraries that were picked in less than 15 minutes. Was this cost effective for the company?
- travisgriggs 2y agoOr "do I even need a library really?" These libraries do what I need AND so many other things that I don't need. Am I just bandwagoning. For my very simple purposes, maybe my own "prefix(n)" method is better than a big ol' library. Or not. All hail the mashup.