Everyone who founds a company needs to remember that they're building a system of systems that all interact and influence each other, and you have to balance short term cash flow against long term strategy.
Everyone who founds a company needs to remember that they're building a system of systems that all interact and influence each other, and you have to balance short term cash flow against long term strategy.
It's not uncommon that this maintainer actually wants to get away from maintaining this code, and would actually be quite willing to teach some successor how everything works.
The problem is that it is often hard to find someone who is similarly passionate about this system (often the system only keeps working because the original maintainer invests a lot of energy into keeping it alive), and is thus brutally willing to learn this system inside out. You can't force this mentality from above: either a suitable programmer has this mentality or he is typically not suitable.
I've certainly inherited and also caused these problems in my younger years.