This article resonates pretty deeply with me, an engineer at a different company Salesforce acquired years ago that, like Heroku, "had resisted integration into

This article resonates pretty deeply with me, an engineer at a different company Salesforce acquired years ago that, like Heroku, "had resisted integration into the larger Salesforce organization and as a result was really really starved for headcount." I joined right when the organization was starting to give in and integrate more, largely out of a combination of need for resources and OG execs having been either replaced or else "org-chart-subjugated" by Salesforce execs, whose influence grew stronger over time. I'm looking towards the door a lot these days. The last few years have been a slow downhill slide, but the last month in particular feels like the edge of the slope where it becomes a straight drop down into the abyss. I've been brushing up on leetcode and polishing up my résumé. As catharsis and to help me process the stress and everything I've been feeling at work lately, I even wrote up a "goodbye" letter in my _personal_ Google Drive account, and I guess this article's author had the same feeling as me, because "my coworkers have left the sinking ship, and it's time for me to get on a lifeboat too" was the exact analogy that came to my mind, which matches the OP's bit about "the ship has been sinking for years but the culture of Heroku really stuck around long enough that it was hard to realize the ship was sinking", and I've felt the same sad realization that the author expresses here as "The Heroku I joined no longer exists. I joined Heroku but I left Salesforce." I joined $acquisition, but my reasons for leaving, once I get it all all lined up, will be Salesforce. It doesn't help that Salesforce has committed to a long-term project with the explicit goal of making $acquisition no longer exist. That just confirms the reality of what I've experienced as being an intentional choice by the company rather than an accident.