Jon Moore
8.6K posts
Jon Moore
@TheJMoore
Principal Product Designer working on Agentforce, Agent Building, Simulation + Evaluation Tools, & AI Platform @Salesforce // Opinions are my own.
Westfield, IN Katılım Eylül 2008
1.7K Takip Edilen6.9K Takipçiler
JOHN HAMM = CURT CIGNETTI
In the movie about the greatest turnaround in sports history!
Who says no?
English
@TheJMoore @MattNorlander Why did the AI hallucinate that IU is a Nike school?
English
Fernando Mendoza's fourth-down touchdown dart is an instantly iconic play and image.
Here are two excellent angles.
LEFT: Kim Klement Neitzel, Imagn Images
RIGHT: Carmen Mandato, Getty Images
English
Working on a smart calendar that adds companion tasks for events that might require planning (for things like birthdays).
It's not helpful to know someone's birthday is TODAY. It'd be great if you got little reminders leading up to it to purchase a gift or make a reservation.
English
@lexfridman Do you think true determinism in AI is something we should preserve, constrain, or deliberately give up in certain contexts, and what are the real tradeoffs when we do?
English
Doing a long, super-technical podcast on the state-of-the-art in AI. Let me know if you have question, topic suggestions. Everything from details of LLM training pipeline & architectures, to coding, robotics, scaling, compute, business, geopolitics, etc.
Besides topics & questions... add papers, blogs, posts, rants, perspectives that you'd like to see covered.
English
@lexfridman As AI systems accumulate long-term memory across interactions, what techniques are actually working in practice to keep behavior predictable and auditable rather than drifting over time?
English
@lexfridman Where do today’s state-of-the-art AI systems draw the line between “memory” and “state,” and how does that distinction affect determinism when the same input is run twice?
English
@dhdresser @Benioff @parkerharris @salesforce @SlackHQ Congrats, Denise! It was great working together at Salesforce the times we crossed paths.
Best of luck!
English
After 14 unforgettable years, I’m grateful to @Benioff, @parkerharris, Rob Seaman, and the entire @salesforce and @SlackHQ ‘Ohana that shaped me as a leader. Leading Slack has been the honor of a lifetime—and I’m proud of what we built together.
I’m excited for what’s next: joining the @OpenAI team as Chief Revenue Officer. OpenAI is redefining how people work, and I can’t wait to help accelerate enterprise adoption and deepen global partnerships.
Looking forward to working with @sama, @fidjissimo, @bradlightcap, Sarah Friar, and the entire team.
More to come!
openai.com/index/openai-a…
English
I can confirm this is the best way to do it. I use Figma and Cursor to build very detailed interactive prototypes of my designs, and it takes a lot of time and care. You have to work slowly, one feature at a time.
There's no such thing as one-shotting unless you're making a page that exists thousands of times in the training set already.
English
A rare honest overview of AI use for designers. I’d like to hear more of these from other designers who use AI heavily.
Tommy Geoco@designertom
After testing every AI toolchain for a year, this is the only workflow I'm endorsing: Figma → Claude Code (Sonnet 4.5) Here's how I'm building Lorelight: 1. Design the happy path in Figma 2. Feed it to Claude Code via Figma MCP 3. Get a strong foundation in 15 minutes 4. Spend the next 50+ hours iterating (still design work) The design/dev loop that used to be isolated is finally closing. I even built a complete design system in within minutes. Custom components, living documentation, accessibility rules all from the Figma designs. If you're measuring the effectiveness of these tools by whether they can "one-shot" a design, you're consuming too many AI hype commercials. Log off. Then go actually build something with your hands. With AI. With your taste. Stop trying to "one-shot" good shit. And go make stuff with the new tools. For designers who want to ship real products, this is the stack that's getting it done.
English
@_dschnurr Pretty genius, because it wasn't at all part of my prompt!
English
I think the real winner in all of this agent building stuff is @xyflowdev 😅
English
OpenAI's AgentKit launch shows the industry is still thinking in old paradigms. Visual builders and drag and drop canvases feel like we're recreating no-code tools from a decade ago.
The real breakthrough will be a conversational agent that lets you describe what you want in natural language and it builds itself. No canvas, no nodes, no workflows.
That's what I'm shipping this week, if you want early access hit me up!
English
a prediction in advance of dev day tomorrow:
agent logic/control flow is going to move down into the API layer, rather than live in your code.
in other words, the agent, not chat turn, will be the API. responses is already designed to support this.
English
this seems very cool but not how I think about agents
an agent should be able to be given tools and decide what to do itself, including spinning off subagents, like Claude Code
these look more like AI powered workflows, like Zapier with LLMs
GREG ISENBERG@gregisenberg
the rumor is openai drops “agent builder” tomorrow and wow, if that's true thats a BIG DEAL for the 12 months, people have been stitching together tools like n8n, zapier, make, vapi, and claude workflows to simulate autonomy. it worked but it was duct tape. now IMAGINE that entire stack, native to openai, with one-click access to MCP, chatkit widgets, and every model they’ve trained (no API chaos. no patchwork. one smooth canvas) this is what happens when ai moves from tool to infrastructure. before: you needed 10 tabs, 5 plugins, and a weekend to build an agent. after: you’ll drag a few blocks, add logic, hit “publish,” and deploy a production-ready workflow. what app store did for software, agent builder COULD do for intelligence. it’s the beginning of the “no-code ai economy,” where building an autonomous agent is as simple as building a notion template. developers get leverage. non-technical founders get superpowers. businesses get workflows that run 24/7 without ops teams. openai might launch the app store for intelligence tomorrow. the DOWNSTREAM effects: - zapier and n8n lose their monopoly on automation - claude and perplexity become upstream research assistants for agent networks - indie agents replace indie apps – data becomes the new code tomorrow's dev day should be INTERESTING.
English