One thing I have truly learned from software development is DON'T REINVENT THE WHEEL. Someone out there may have already implemented such functionalities and if the library is missing something a PR is always welcomed! (Obviously taking about open source libraries)

And sometimes the documentation is so lousy, the build doesn't work and the dependencies are so vast that I say fuck it and roll my own solution because that's faster.

@Fast-Nop exactly

@shahidcodes I remember that kind of shit with Srecord, a tool that is supposed to deal with hex files and CRCs and shit. The devs were even smug assholes as per their documentation.

"No build for Windows, hahaha" and picture of crying baby. Plus that they mock about stupid EEPROM programming devices that can't handle more than 16 bytes per hex file data line - and these dumbnuts use 32 bytes as default in their tool, fully knowing that users will run into difficulties. And who knows what other bad jokes they put in their code.

Yeah and under Cygwin, the deps ran deeper than the roots of an oak, and still didn't even compile. I don't want make my project depend on such shit because nobody would be able to set up that toolchain.

400 lines of C code later, I had exactly the part of Srecords' functionality that I needed, without deps. Of course with 16 bytes per data line so that any programming device will cope.

And filing PRs with open source projects? The main use for that is that I can document strange workarounds on my side with reference to the PR. Open source PRs mostly don't get fixed, not even with clear test case. Instead, they rot for 2 years and then get closed because they are outdated. Not that a project stakeholder would bother testing with the current version. Works for me & scratch my itch & fuck any kind of QA.

And that's why I try to minimise external dependencies on shit - I'd have to fork and maintain myself anyway.

This is a valid thought, but also don't reuse the will that hasn't been updated in years. A past coworker introduced a dependency to our app that hadn't been updated in 2 years at the time (5 now). Currently it's breaking all our builds due to an update and I have to go back and extract/ reinvent what feels like 3 wheels now

@Fast-Nop completely true .