this post was submitted on 18 Jan 2024
666 points (98.0% liked)
Programmer Humor
32479 readers
253 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I would say finding that the bug is in a library is worse than finding it in your own code.
If it's your own code, you just fix it.
If it's in a library you then have to go and search for issues. If there isn't one, you then go and spend time making one and potentially preparing a minimum reproducible example. Or if you don't do that (or it's just unmaintained) then you have to consider downgrading to a version that doesn't have the bug and potentially losing functionality, or even switching to another library entirely and consequently rewriting all your code that used the old one to work with the new one.
Yeah, I'd take my own bugs over library bugs any day.
That’s where my ecosystem shines, since it’s all open source. If there’s a bug that I can fix, but the maintainer won’t, I’ll just fork the repo.