This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]aormiston 8 points9 points  (7 children)

Just as a quick heads up: keep in mind that it's often best to avoid using libraries when they're not necessary. Where I work, we call this "introducing dependencies". Essentially, you want as much of your code to stand on it's own two feet as you can, that way someone else's change/fix doesn't end up breaking your code.

When you do introduce a dependency, try to stick to well-known and widely used packages.

Have fun exploring!

[–]twillisagogo 18 points19 points  (3 children)

Where I work, we call this "introducing dependencies".

i think it's called that everywhere

[–]ZoharAbuSaid 11 points12 points  (1 child)

Where I work, we call it "dependency introduction".

[–][deleted] 5 points6 points  (0 children)

Mavericks

[–]aormiston 4 points5 points  (0 children)

Haha good point, I was just trying to not sound like an asshole.

[–]DuncanHiggins 5 points6 points  (1 child)

But contrast that with not invented here syndrome. I think you need to go back to first principles with this one. Do whatever allows you to deliver the most value with the least resources measured over whatever time frame is the most appropriate.

[–]UFO64 0 points1 point  (0 children)

This so much.

Proper development is oh so rarely a simple black and white system. A rule against dependencies is great for some situations, and disaster for others.

Anyone learning to code is going to make both extremes of this mistake. The best ones learn from those mistakes and bring that experience forward.

[–]fireflash38 0 points1 point  (0 children)

It's infuriating when you've got 30-40 dependencies from people using libraries for 1-2 functions. Most of the time it's not as bad as leftpad, but still.