Comment

Comment by time_to_smile

I'm surprised how long the "solution in search of a problem" trend has dominated tech product design, despite obvious and repeated failures of this approach to produce results.

AI/ML products fundamentally don't make sense compared to products that happen to use some AI/ML to aid in solving a problem.

It's sort of like loving to use redis (which I do) and thinking you want to found a company based on using redis in the product, or start a redis product team, dedicated to shipping products that use redis.

It's one thing if you want to host redis as your business, which is solving a problem involving redis, but if your aim is to use redis to solve a problem then you're going to be in trouble.

Imagine a PM on the "use redis" team rejecting a great idea for customers because it could be more efficiently solved using a traditional database, or forcing the use of redis when a cheaper, easier solution already works just as well if not better. This is actually the case on AI/ML teams.

GPT startups that will thrive are the ones that aren't GPT startups, but instead solving some other, real, problem that happens to only be solvable in a post-GPT word.

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton