Hmm well I get that we're in an asset bubble with startups, but if this company is creating jobs, then I think it's somewhat reasonable to assume that they are fixing a problem ppl are willing to pay for.

I do agree with what you're saying from my perspective as an average swe that doesn't do anything highly specialized...

I wonder though, what would the workflows look like for a swe, product, ops person even, where schema changes get passed around and edited so much, (kind of making some assumptions here, comparing central schema registry to crm use cases), that this would be necessary...

Wonder what the shape of the problem looks like...