What's WILD is people ending up relying on these essentially startup-slops that just serves to give you future technical debt once you have to eventually moved away because they got acquired by $INSERT_BAD_GUY_OF_THE_MONTH
The only people "relying" on this are other startups whose VC benefactors force them to use other products under their portfolio in order to goose up their numbers.
that makes so much sense. I always wondered how the fuck did all those ZIRP era "hello world as a service" bullshit startups have any customers at all.
It may be that there are many projects relying on Stainless, or, as a sibling comment points out, it may be portfolio-based stack selection rather than actual feature dependence.
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.
What's WILD is people ending up relying on these essentially startup-slops that just serves to give you future technical debt once you have to eventually moved away because they got acquired by $INSERT_BAD_GUY_OF_THE_MONTH
The only people "relying" on this are other startups whose VC benefactors force them to use other products under their portfolio in order to goose up their numbers.
that makes so much sense. I always wondered how the fuck did all those ZIRP era "hello world as a service" bullshit startups have any customers at all.
1 reply →
I've raised venture from a lot of the big firms (and a lot of small firms) and have never had any of them attempt to force me to use anything.
5 replies →
Stainless was a fantastic product; every product/service has to start from somewhere
It may be that there are many projects relying on Stainless, or, as a sibling comment points out, it may be portfolio-based stack selection rather than actual feature dependence.
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.
They didn’t. The first is from the Stainless blog post, the second is from Anthropic’s.