Загрузка видео...

Не удалось загрузить видео

На главную

Everyone is still optimizing prompts The people running 20 agents stopped doing that a year ago Prompt → Context → Harness → Loops Matt Pocock put his whole workflow in one hour and called it "just copy him" 384,000 watched it, almost none copied the third layer a rule...

74,307 просмотров • 16 дней назад •via X (Twitter)

Комментарии: 13

Фото профиля Matt Pocock
Matt Pocock16 дней назад

God this slop-repost meta is boring, can't you add something new to the conversation?

Фото профиля Jordan | 先生
Jordan | 先生16 дней назад

Well, yeah, fair enough. However the breakdown under it isn't a repost though, my own article with 10 steps, diagrams etc If any of it is wrong I'd rather hear it from you than not.

Фото профиля Matt Pocock
Matt Pocock16 дней назад

I just don't understand why you're using my face to advertise your article Just post your article If it's good, it'll get attention

Фото профиля gsimone
gsimone16 дней назад

@mattpocockuk > bookmark it before it's gone what

Фото профиля Jordan | 先生
Jordan | 先生16 дней назад

@mattpocockuk bookmark this tweet before it's gone in your timeline

Фото профиля Anders Abjorn | sales → AI
Anders Abjorn | sales → AI16 дней назад

@mattpocockuk It's a difference To prompt like it's Google and works with AI like AI is supposed to be used

Фото профиля Danny Yaroslavski
Danny Yaroslavski16 дней назад

@mattpocockuk Stop tweeting like an llm

Фото профиля AI Mastery Guide
AI Mastery Guide16 дней назад

@mattpocockuk Almost nobody copied the layer

Фото профиля AJ ◥
AJ ◥16 дней назад

Grok, full technical breakdown: thesis, 5 core arguments with timestamps, 3 counterpoints, lessons, methodologies with paper links, tools/platforms, cited researchers/companies, 2 direct research-team applications, SOTA gap, and implementation details (hyperparams, architecture sizes, or costs) if mentioned. No fluff.

Фото профиля badbutar
badbutar16 дней назад

@mattpocockuk Prompts are suggestions, harnesses are the bouncers

Фото профиля CryptoAI_Insider
CryptoAI_Insider16 дней назад

@mattpocockuk Most people build fragile agents because they skip the harness entirely.

Фото профиля hylanderdev
hylanderdev16 дней назад

@mattpocockuk At least unslop your content before posting lmao

Фото профиля DEV
DEV16 дней назад

@mattpocockuk Most are stuck at the prompt level. The real value’s in those deeper layers.

Похожие видео

Harness vs. Graphs, clearly explained! a harness is great, and most people think it is the whole thing: retries, timeouts, a sandbox, a log, the context it assembles before every call. all of that is real work, and all of it wraps exactly one call. run it a hundred times and you have one call, made very safely, a hundred times. Graph engineering fixes this by moving the decision up a layer: not how safely one call is made, but which calls exist to be made at all. you need both, and here is the sentence that resolves the whole confusion: the harness is everything around one call. the graph is everything between them. ↳ around one call: retry, timeout, sandbox, log, assemble the context, hand back a result ↳ between calls: split, fan out, merge, gate, send back Prompts → Context → Harness → Loops → Graphs the harness does not go away when you build a graph. it moves under each node, and now there are five of them, each wrapping a call you would never have made by hand. the trick is knowing which layer a failure belongs to. turn a piece off and run it again. if the call still works, it was the harness. if the wrong step runs at all, it was the graph. people spend weeks hardening a harness around a node that should not have existed. one thing to know before you scale it. most of what people call their agent is a harness with a chat box on it. ↳ it retries, it times out, it logs, it assembles context, it holds one call up beautifully ↳ it has never once decided that a second call should exist, and that is the entire difference that last one catches careful people. a harness that never fails is not evidence the system is right. it is evidence one call went well, which is the smallest possible claim. and the one that eats whole nights: a harness cannot save you from the wrong step running. you can retry a bad decision three times with a clean log and perfect isolation, and all you bought was three copies of it. below i have quoted my full guide on graph engineering. it covers the three topologies, the verifier patterns, and where the gate should actually open. save this and read it below ↓

Hanako

50,770 просмотров • 9 дней назад