3 ms·
> The experienced also don’t mind digging into code I only got this pretty recently. For the longest time, something did not work, I would try to look for an o
by Derbasti 15y ago
> The experienced also don’t mind digging into code
I only got this pretty recently. For the longest time, something did not work, I would try to look for an obvious cause but more often than not, I would not find anything and just give up.
More recently though, I observed myself quickly finding the code in question and usually am able to figure out the issue, too. From there, you can see how much effort it would be to fix it. This is amazingly awesome! I absolutely love it!
It really devaluates closed source software for me. If something in Matlab or Cocoa is broken, tough luck for me. If it's broken in Numpy or Qt, I can deal with it and either circumvent it or directly fix it because I can read the source. Invaluable.
- jiggy2011 15y agoThe problem is though, that once you have done your fix. What then? Do you try and give it back to the developers, what if they reject it? You are then in a situation where you are maintaining your own version of library X for your own project. What happens if a new version comes out with significant changes? Do you try and merge your version back together with it?