5 ms·
Or worse, the developer gets bored and stops supporting the project, and it stagnates until it breaks everything else. VisionEgg I'm looking at you.
by jonnycomputer 7y ago
Or worse, the developer gets bored and stops supporting the project, and it stagnates until it breaks everything else. VisionEgg I'm looking at you.
- caymanjim 7y agoExcept that happens far more often when you roll your own code internally. For anything of even moderate complexity, only the author will know how it works.
- clarry 7y ago> For anything of even moderate complexity, only the author will know how it works. I think that's as much true of external dependencies as it is of ones that you wrote for yourself. With the exception that your own solution is probably smaller, much smaller, because it only ever needed to solve your immediate needs and not everything else a third party had to deal with. So it's quite possible that the internal solution is more approachable when the time comes to debug it.
- deleted 7y ago[deleted]
- hinkley 7y agoIf this person is bad at knowledge transfer, they end up being the only expert and thereby gaining status for having done so, when objectively this should cost them status instead.
- hinkley 7y agoInternal people do this too, but often don’t have the stones to admit they got bored. Instead they victim blame and try to prop up their status as the smartest person in the room. Personally I’d rather be mad at someone I’ll never meet. It makes meetings a lot more pleasant.