When I Leave Tech I'll Train My Replacement

One day I'll leave tech.

There, I said it. It might be career suicide, but I like to think that my value as an employee is in the quality of work I produce. If my employer learns that in X year's time I'll leave, so be it. It has been an amazing run; I honestly didn't think I'd make it this far. It started out so promising: Work that involves solving problems at a high pay, what kind of nerd wouldn't love that? Lately, though, the luster has left me. I can't remember the last time I wrote code outside of work. I can't remember the last time being excited about learning a new technology. I can't remember the last time whiteboarding a system sounded like fun. I thought maybe switching jobs would help, but two more jobs later I feel equally empty. It won't be this year, it won't be next year, but I'm going to leave. However, I'm holding myself to a stipulation if I leave:

When I leave tech I'll train my replacement.

Why? Because there's someone out there who codes outside of work who would love the opportunities I had. Because there's someone out there who's going to meetups about the latest technologies. Because there's someone out there who is dreaming up of new systems and whiteboarding them to audience of one. They deserve to be where I am. I want to make it happen for them.

Author: Patrick Brown

Created: 2018-03-25 Sun 23:43

Emacs 25.3.1 (Org mode 8.2.10)