I once worked as the sole maintainer of an old legacy product while the company spent 2 years trying to create a new product to replace it. Eventually they abandoned all work and most of the team left.
During the transition months, I managed to convince upper management that now would be a good time to update the legacy product with all the knowledge gained over the past years.
So I spent about a couple of months or more (fuzzy memory) directing a group of people more skilled and talented than me, converting a coffeescript codebase to typescript, fixing a whole bunch of bugs and performance issues and updated a neglected codebase to something they can actually hire people to work on.
After that experience, I was promoted to tech director and leveraged that to become tech lead at future jobs.
Thanks for the example. I suppose that's a fairly unique position to be in, but one that you could have chosen not to pursue. On the surface, the only way that's different than my most recent experience is that of being the director of the initiative, or otherwise responsible for the whole project, (also being laid off doesn't help). Do you think things would have gone differently had people not jumped ship?
It's definitely a case of 'right time, right place'. But I also had several factors that helped increase my luck surface [0].
- I had experience with early versions of angular.js (1.2~) and typescript (1.x~)
- I was willing to dive into an unknown codebase in an unknown language (coffeescript 1.x) that no one else wanted to touch
- I had almost a whole year to get familiar with the codebase, the intricacies and weird bugs, and the crazy amounts of OOP in it
- I came from the old definition of full stack (design + dev + database + user facing), making me a generalist among a bunch of technically minded people
Also, everyone was pretty demotivated and mentally checked out. Some had spent 2.5 years working on the project, there was a public launch for the beta release, press releases and a whole PR event to our existing users. Less than a month later, the board/investors cancelled the project. Even the CTO was pretty checked out and let me do whatever I want, which was probably how my crazy proposal got through. Within 2 months, we lost the entire upper senior engineering division, from CTO down to team leads. There was a huge debate about whether or not to even keep the engineering division, if it would be better to sell our current product to our rivals and re-focus on being a design agency. That didn't happen because our rivals came to us first asking if we would buy them...
During the transition months, I managed to convince upper management that now would be a good time to update the legacy product with all the knowledge gained over the past years.
So I spent about a couple of months or more (fuzzy memory) directing a group of people more skilled and talented than me, converting a coffeescript codebase to typescript, fixing a whole bunch of bugs and performance issues and updated a neglected codebase to something they can actually hire people to work on.
After that experience, I was promoted to tech director and leveraged that to become tech lead at future jobs.