←back to thread

A PM's Guide to AI Agent Architecture

(www.productcurious.com)
205 points umangsehgal93 | 1 comments | | HN request time: 0.199s | source
Show context
ramesh31 ◴[] No.45130377[source]
Stop trying to treat these things as more than they are. Stop trying to be clever. These models are the single most complex things ever created by humans; the summation of decades of research, trillions in capex, and the untold countless hours of thousands of people smarter than you and I. You will not meaningfully add to their capabilities with some hacked together reasoning workflows. Work within the confines of what they can actually do; anything else is complete delusion.
replies(2): >>45130538 #>>45131022 #
sixo ◴[] No.45131022[source]
This is a nonsensical opinion by a person who doesn't know what they're talking about, and probably didn't read the article.

These models are tools, and LLM products bundles these tools with other tools, and 90% of UX amounts to bundling these well. The article here gives a great sense of what this takes.

replies(2): >>45131714 #>>45131742 #
CuriouslyC ◴[] No.45131742[source]
The AI bundling problem is over. The user interface problem is over. You won't need a UI for your apps in a few years, agents are going to drive _EVERYTHING_. If you want a display for some data, the agent will slap together a dashboard on the fly from a composable UI library that's easy to work with, all hot loaded and live-revised based on your needs.
replies(5): >>45131916 #>>45131951 #>>45132407 #>>45132431 #>>45133170 #
1. tomrod ◴[] No.45132431[source]
I won't use agents for everything. Why would I expect tasks to use agents for everything? This is like saying everything is on the web. No, there is substantial number of things on the web, but not everything.