3 ms·
I have plenty of utilities that I've written over the years that work perfectly on my machine, but I know they'll probably fail on some else's due to hardcoded
by mattowen_uk 5y ago
I have plenty of utilities that I've written over the years that work perfectly on my machine, but I know they'll probably fail on some else's due to hardcoded file paths and assumptions as to what libraries are installed.
The thing is, there's a big difference between writing something for your use case, and writing something for others.
- dTal 5y agoUh huh, and did you release binaries of those utilities for public consumption?
- mattowen_uk 5y agoNope. Because as I said, they wouldn't work, due to the hardcoded file paths etc. Expanding on this further - I have a few apps I've written out there in the wild, and for one (which also found it's way onto a magazine cover CD-ROM back in the day) I had immense pressure to open source it, so against my better judgement I did. I then had to endure lots of negative feedback about the quality of my code. The whole experience put me off going open-source ever again[1]. I am a hobbyist coder, and my code quality will never be 'up there' with the professionals, but the moment you release something (even for free) people expect it to be perfect, which is unrealistic. --- [1] Not quite true, I do have a GitHub with a few tiny repos, but nothing important.