Do you carefully consider the technical debt implications of introducing dependencies to your code before adding it to your code?

If you answered this either way, please leave feedback behind your justification in a reply to this toot.

· · Web · 6 · 0 · 1
@cadey if I'm writing code I'm expecting people to be using for years and years, I sure wouldn't pull in some hack library made in a rush and uploaded for Github points

perhaps a bit salty but being honest 

@cadey I don't think that I CAN do so

What does it mean to consider it?
Things I write myself might not be maintained much
Things I import might never get updated
Projects these days aren't often from big reliable organizations and the "just grab a package" attitude + |batteries NOT included" way of thinking has lead to fractured features, accidental library lock-in, and word-of-mouth programming

Its honestly an impossible nightmare for me

@cadey I add as few dependencies as possible, and when I do I carefully inspect the dependency itself, the implication and behaviour of its maintainer(s).

@cadey If there's a dependency, it'll cause me problems, so I try to minimise the number of dependencies.

If I'm considering a dependency that brings in a thousand others? I'll generally re-consider.

@cadey No, alas, as I'm usually hyper-focused on delivering new/any functionality in my personal projects/line of work.

@cadey I've been bitten too many times by additional considerations when it comes to updating. Upgrading dependencies can be troublesome, especially when coupled with upgrades to the runtime or stdlib forcing lock-step major-version changes of those dependencies.

Sign in to participate in the conversation
Interlinked MST3K

this is mst3k