Many users dismiss loop engineering as hype, rebranded retry loops, or performative AI terminology invented for attention, while some value adversarial workflows and autonomous agents for handling development tasks.
Based on 11 visible X reactions from 104 accounts; directional sample.
Ask a question below.
Published answers will appear here.
@GergelyOrosz concretely: i was building a non trivial sync, replay, and conflict resolution engine for https://github.com/jul-sh/clipkitty Using a single model, the results were consistently buggy; even with a lot of human back and forth. With captain codex it finally worked.
@GergelyOrosz I doubt 99% use loops because they're really needed. It's a hype created by oai/ant because internally they have an infinite number of tokens they can use and using loops leads to even more token consumption which is good for these companies.
@GergelyOrosz i like adversarial workflows for plans and PR reviews. so the 'loop' is: model A and model B both make independent blind plans, model C adjudicate/synthesizes a final plan/review (or maybe a rotation of A/B if you don't have a good C).
@GergelyOrosz “Loop engineering” is yet another attempt at reinventing terms to farm some karma on X. And since lot of people have huge FOMO about agents it finds an audience 🤷♂️
@GergelyOrosz concretely: i was building a non trivial sync, replay, and conflict resolution engine for https://github.com/jul-sh/clipkitty Using a single model, the results were consistently buggy; even with a lot of human back and forth. With captain codex it finally worked.
@GergelyOrosz I doubt 99% use loops because they're really needed. It's a hype created by oai/ant because internally they have an infinite number of tokens they can use and using loops leads to even more token consumption which is good for these companies.
@GergelyOrosz i like adversarial workflows for plans and PR reviews. so the 'loop' is: model A and model B both make independent blind plans, model C adjudicate/synthesizes a final plan/review (or maybe a rotation of A/B if you don't have a good C).
@GergelyOrosz “Loop engineering” is yet another attempt at reinventing terms to farm some karma on X. And since lot of people have huge FOMO about agents it finds an audience 🤷♂️
@GergelyOrosz The current level of AI bros speedrunning software development concepts from fist principles. We have now reached the 60s...
@GergelyOrosz The word "Engineering" has lost its meaning with every Ai hybed concept
Yeah, "events engineering" aka "start an agent when an event triggers" makes tons of sense to me. Not all that different from other automations we had, even pre-ai... webhooks, Zapier, bots (incl Slack bots) etc... feels like the main use case tbh? https://x.com/Amehmeto42/status/2076603257003409601
Daily reconciliation is NOT a good use for agents fwiw, but a very good use of deterministic automation (aka scripts running!). B/c agents are nondeterministic.... And daily / EOD reconciliation is a decades-old concept, great use case for cron https://x.com/YashAtreya/status/2076606449212625274
Yes the one I hear most often is the periodic work: 1. Nightly runs (e.g. tackle a piece of tech debt, and have a review ready by the morning) 2. Weekly, larger runs to eg improve a system https://x.com/_mayy00_/status/2076595147458990292?s=20
What is "loop engineering" to you, anyway? Been looking into this, and also experimenting myself... and I'm not (yet?) buying that it's a new paradigm. But I might just be missing something. Can you share "loops" you regularly use?
Many users dismiss loop engineering as hype, rebranded retry loops, or performative AI terminology invented for attention, while some value adversarial workflows and autonomous agents for handling development tasks.
Based on 11 visible X reactions from 104 accounts; directional sample.
Ask a question below.
Published answers will appear here.
@GergelyOrosz The word "Engineering" has lost its meaning with every Ai hybed concept
Yeah, "events engineering" aka "start an agent when an event triggers" makes tons of sense to me. Not all that different from other automations we had, even pre-ai... webhooks, Zapier, bots (incl Slack bots) etc... feels like the main use case tbh? https://x.com/Amehmeto42/status/2076603257003409601
Daily reconciliation is NOT a good use for agents fwiw, but a very good use of deterministic automation (aka scripts running!). B/c agents are nondeterministic.... And daily / EOD reconciliation is a decades-old concept, great use case for cron https://x.com/YashAtreya/status/2076606449212625274
Yes the one I hear most often is the periodic work: 1. Nightly runs (e.g. tackle a piece of tech debt, and have a review ready by the morning) 2. Weekly, larger runs to eg improve a system https://x.com/_mayy00_/status/2076595147458990292?s=20