For context I was the founding member of our customer eng team, the main drive for Stainless adoption came from engineering teams who didn’t have the time/capacity/expertise to implement high quality SDKs + maintain the whole release pipeline automation across multiple languages. The pitch is „we want you to focus on your domain of expertises. We handle all the plumbing for your end users to have the best DX possible when using your services“. Which is IMHO very compelling
Either way, it does seem irresponsible and tone deaf for an acquiring/hiring company and an acquired/hired company to send these conflicting signals. If one puts oneself out there as dependable in the face hopes and needs of other, smaller, up-and-coming projects, then a rapid wind-down for $ is incongruent with such a posture.
So much so that, at least for my part, I'd be quite reluctant to hire someone who had engaged in this sort of bob-and-weave pursuit.
