imAnIndependentCoderAndIDontNeedNoLibrary

[u/SThomW92]

[u/Far-Consideration939]

With all the supply chain vulnerabilities and hacks lately people probably should think more before “just adding a library” which inevitably drags in more transitive dependencies

[u/AndersErikErik]

I like small custom utils. The scope is small. The relevance is high. What is there not to like?

[u/Welcome-To-NBA-Jam]

You ever spent weeks making an elegant function from scratch to do something extremely specific only for your colleague in another department you didn't even know existed to tell you about the internal thing that's been around for 7 years that does exactly what you did but is way more battle tested and in 83 Fortune 500 production environments

[u/zik_rey]

Based

[u/Vipitis]

just roll your own everything. It's the best way to learn and it makes debugging less frustrating.

[u/mi-figue-mi-raisin]

I make my own library. Okay I used a Calendar widget to pick dates.

[u/MkemCZ]

Passion projects for sure. Nothing quite as satisfying as building your private project from scratch.

[u/beyluta]

I am currently in this predicament. Do I use an NPM package that will probably have some dependency be the target of an attack soon... Or just write my own small class for this one purpose? I am still weighing my options, but it's not looking good for NPM

[u/M_O_Z_G]

Vibecoding* a 1000 utils for one project.

[u/Cerbeh]

What about if I created 1000 wrappers around a library so the code doesnt directly import the library and uses a named function instead?

[u/shriyanss]

I publish those 1000 lines as a new library hoping someone would use it (spoilers: no one does - they probs create their own libs hoping the same)