Post

Pretty sure that soon you'll need GenAI for your app as often as a database. And the same concerns apply. Security, performance, observability. A lot of devs are going to need to upskill.

1 repost41 likes

Recommendations, relational search, autocomplete, will become table stakes. More users will want chat interfaces. AI features are an easy 'pro' tier upsell to any app.

I agree about most of that, but not chat. Chat is a great stopgap for developers/product teams who haven't figured out the right happy path yet, and want to let their users find it. But once you've found it, UI ("book now" button) beats AI (typing "b-o-o-k-n-o-w") every time.

That's what we found empirically when I was working on AI chatbots at Microsoft (admittedly "early" AI, pre GPT). People liked when chatbots enabled new functionality - and AI was great for shipping new stuff fast. But for any given functionality it was just not efficient UX.

“Recommendations” is a huge field in itself. If you build a RAG for a book store that detects fraudulent books, that’s a “recommendation” engine too, that shows moderators books they should keep an eye on. Similarly with comments, spam, etc.

I've seen a lot of value in it from a Big Data perspective, but outside of that LLMs and other AI services are almost the entire product, not just tacked on. I'm curious why you believe people want "thing I can already use", but via a chat interface (and how that improves the user experience)?

I don't - GenAI is useful for MUCH more than chat interfaces. Improving search, recommendations, summarizing large datasets and QA-ing important data fields are the obvious ones for me.

I agree with your broader point about GenAI being a skill set that people should have. It's a tool developers _can_ reach for, but my concern is that they're being used without the consideration of a tangible benefit to the customer/user; Google being an amazing example of it whiffing.