At the end of the day, the stack is collapsing itself, and the lines are blurring because we want people to own the total outcome more often than throwing responsibilities over the wall to each other.
That doesn't mean engineers are going to design, but they should know what a good design looks and feels like. That doesn't mean designers or product should write code, but they should be able to engage in high level architecture discussion to understand the capabilities of their products.
I have not read it yet but there's a book by David Epstein (not that one), "Range: Why Generalists Triumph in a Specialized World". I'm interested because for the last 10 years I've thought of myself as a generalist but always thought companies were looking for specialists. I could show immense value when I got to those companies, but I don't typically think companies are looking for generalist. They are looking for specialists to solve an acute problem.
I thought it was interesting to think about what Clubhouse was displacing. It felt the most analogous to radio. So, what could you do if you had radio at internet scale? Or what would it take to make internet scale radio successful?
In my mind, it came down to how challenging it would be to produce and monetize content. It's non trivial work. Producing a good radio show that's worth listening to takes a lot of time and effort. Podcasts are a good example here. I think there's data out there that suggests most podcasts don't have more than 1 episode or survive the first year. Without a good way to monetize, it's not worth the effort.
So while easy in the short term for celebrities/influencers/celebrities/VCs to jump on the bandwagon, the effort wouldn't be sustainable or worth it to them in the long run, and then you have a content problem again.
I also experienced some dark onboarding patterns while I checked it out that make me suspect their growth numbers were a bit over inflated, in an ask for forgiveness later kind of situation.
At the end of the day, the stack is collapsing itself, and the lines are blurring because we want people to own the total outcome more often than throwing responsibilities over the wall to each other.
That doesn't mean engineers are going to design, but they should know what a good design looks and feels like. That doesn't mean designers or product should write code, but they should be able to engage in high level architecture discussion to understand the capabilities of their products.
I have not read it yet but there's a book by David Epstein (not that one), "Range: Why Generalists Triumph in a Specialized World". I'm interested because for the last 10 years I've thought of myself as a generalist but always thought companies were looking for specialists. I could show immense value when I got to those companies, but I don't typically think companies are looking for generalist. They are looking for specialists to solve an acute problem.