That seems harsh, unless FT no longer generates any income.
Less that and more just corporate priorities.
So a little inside baseball:
- FT does not generate more revenue than all the rest of travel combined, so it makes more sense long-term to have a single Likes product that is shared by all sites and no tech worker needs specific, separate knowledge on
- No one that worked on the FT Likes is with the company or in our department anymore.
- While the new team can devote a lot of time to trying to figure out any current bugs, the next time we have a site update or even a change in a minor code, there could be a new bug, which would then require more dev hours, who may be new and need to re-familiarize themselves with the product, taking time away from other tech projects
- Since we have a different, standardized, completely working product to replace it, it makes way more sense to just switch over to that
- Now I know you guys hate the design of the new product, so I've been holding it off. But if the Auto Communities tech team doesn't fix the design by the time FT Likes becomes completely broken, then we'll be stuck with that
- As you may realize, fixing a relatively minor design issue for a single site that isn't even in their portfolio is not a high priority for them