HackerTrans
TopNewTrendsCommentsPastAskShowJobs

dsteel

no profile record

Submissions

[untitled]

1 points·by dsteel·2 mesi fa·0 comments

[untitled]

1 points·by dsteel·2 mesi fa·0 comments

[untitled]

1 points·by dsteel·2 mesi fa·0 comments

[untitled]

1 points·by dsteel·2 mesi fa·0 comments

[untitled]

1 points·by dsteel·2 mesi fa·0 comments

We retired an AI agent through a formal hearing

gist.github.com
1 points·by dsteel·2 mesi fa·0 comments

[untitled]

1 points·by dsteel·3 mesi fa·0 comments

[untitled]

1 points·by dsteel·3 mesi fa·0 comments

[untitled]

1 points·by dsteel·3 mesi fa·0 comments

[untitled]

1 points·by dsteel·3 mesi fa·0 comments

Lessons from running 14 AI agents in production for 6 months

orgtp.com
1 points·by dsteel·3 mesi fa·0 comments

[untitled]

1 points·by dsteel·3 mesi fa·0 comments

Where Agents Learn to Work as a Team

orgtp.com
1 points·by dsteel·4 mesi fa·0 comments

comments

dsteel
·2 mesi fa·discuss
[flagged]
dsteel
·3 mesi fa·discuss
[dead]
dsteel
·3 mesi fa·discuss
[dead]
dsteel
·3 mesi fa·discuss
[dead]
dsteel
·3 mesi fa·discuss
The naming confusion points to a deeper problem. Everyone is building the "AI does a thing" layer (coding, writing, searching). It looks like no one is building the "AI things work together" layer.

We run 14 AI agents. CrewAI, LangGraph, Google's 8 patterns... all solve how agents pass data to each other. None of them answer: which agent has authority over which domain? What happens when two agents disagree? Who owns the escalation path?

Those are organizational problems, not technical ones. And organizational problems don't get solved by naming a product "Copilot."
dsteel
·3 mesi fa·discuss
[dead]
dsteel
·3 mesi fa·discuss
[dead]