Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@Lensflare Yes, isn't it? But he doesn't seem to be a rookie. The library works fine and fast, there are no weird bugs or issues so far. The support from him is nice and responsive. The lib is on the market since 2001 and even has won some awards. Don't know what happened here. I guess the code is as old as the library itself.
-
Unfortunately from an auditor's point of view, "some-library": "1.2.3" is one very clear and simple line of code, whereas if you wrote the functionality yourself that would be hundred of potentially complicated lines.
Now you may be tempted to say "in that case the auditor is a retard", and you would be correct, but if you say that then the auditor will go through everything you're working on like a dose of the clap.
Obligatory mention of leftpad. -
@donkulator Yup and the manager being afraid "to waste effort"/don't re-invent the wheel even when the lib is a buggy piece of shit (yes I'm still salty about it filling sentry/slack with errors)
-
Yeah, but also be honest guys, how often do you review a lib? Normally it doesn't go further than checking active development what actually says nothing. Think about it. Some libs are just done. But for sure, nobody is reading up the dependency of the dependencies. Also, in this new era where it is so simple to look up how things are done, all the "secrets" of those libs are in the open now. Ready to be implemented yourself.
-
@whimsical to be fair, in most cases we use libs not because we can’t write the code ourselves but because we don’t want to.
And most libs don’t try to keep their code secret anyway. -
@Lensflare that's true, but many times I think, hmm, how hard can it be. These days you can check it so fast. But also, I do not code professionally anymore and I have all the time to spent a day on failing implementing something already existing.
Stackoverflow.
when your code is a mess but everything work out in the end
When you keep getting +1s on a rant you posted a month ago.
I'm working on a project that uses a 3rd party library. We've got the source code to that library and I'm exploring its code, looking to find out how the author did something. I just discovered a Paint function that has over 7,000 lines of code, with nested sub routines, awful indentations and line spacings and lots of IFDEF conditions ... Wow, I'm amazed that this thing works at all and I'm wondering how the author is even able to maintain that code.
devrant
programming
delphi
rant
technical debt