This question already has an answer here:
- How can I prepare for getting hit by a bus? 13 answers
A little over two years ago (about a week after being hired into my first job), I was asked to improve a system used by our office. It was supposed to be a quick and easy thing, maybe two weeks. I end up (with managerial approval), doing a total overhaul of the system and sinking about 6 months into it. I can now confidently it is my system. I have a casual understanding of programming (I'm an engineer), which I used in my overhaul. The system works, but its not error free, and it hiccups often enough that without me, it would not function. I am now considering leaving, but am concerned about leaving my office high and dry. The way I see it, I have a few options:
- Cut and run: Leave the system as is, if it breaks, its not my problem anymore, and I should just live with any potential negative reputation this may give me.
- Offer to do my best to train someone on how to work with the system: This would take time (I would need to do this well before my two weeks), and likely wouldn't fix the problem fully (I am not confident in my coworker's ability in programming)
- Offer to continue to work with the system even while at a new job: This option means I'll be giving up nights and weekends to fiddle around with code that someone else owns, but no one will ever be able to call me apathetic. As an aside, a friend suggested doing this and charging the company, but that sounds a lot like blackmail to me.
How do I professionally turn over control of a utility when changing jobs?