4 ms·
And so what do you do after "figuring out why" when you're not actually free to modify the software?
by filleduchaos 7y ago
And so what do you do after "figuring out why" when you're not actually free to modify the software?
- bryanrasmussen 7y agowell often when I read the source of a library (or tool or framework or what term we wish to use), even one that I am free to modify the source of, I will see that the way I thought I was going to solve my problem was not the way to do it and I will need to alter my code not the code of the library. In a few occasions I see that I need to alter the library, if I do not have the rights to do that then I would probably end up dropping the library as being inadequate to the task. In some occasions I have seen that I would like to get rid of the library but I am generally not allowed to by other business decisions, in those cases I have always been able to find some hack that allows me to do what I need to even if it goes against the preconceptions of the used library. I then make extensive comments in my code explaining why, probably referring to the other solutions I would prefer to use and explaining why I was unable to do so. Why? What do you do?