Looks like all bullshit to me. When you try to make up complex terms to pretend that you are doing engineering but it is baseless.

Something like if I do a list of dev pattern and I say:

- caffeinated break for algorithmic thinking improvement

When I'm thinking about an algorithmic logic, go to have a coffee break, and then go back to my work desk to work on it again.

Here is one of the first "pattern" of the project I opened for example:

   Dogfooding with rapid iteration for agent improvement.

   Developing effective AI agents requires understanding real-world usage and quickly identifying areas for improvement. External feedback loops can be slow, and simulated environments may not capture all nuances.

   Solution:

The development team extensively uses their own AI agent product ("dogfooding") for their daily software development tasks.

"Extended coherence work sessions"

   Early AI agents and models often suffered from a short "coherence window," meaning they could only maintain focus and context for a few minutes before their performance degraded significantly (e.g., losing track of instructions, generating irrelevant output). This limited their utility for complex, multi-stage tasks that require sustained effort over hours.

   Solution
   Utilize AI models and agent architectures that are specifically designed or have demonstrably improved capabilities to maintain coherence over extended periods (e.g., several hours)

Don't tell me that it is not all bullshit...

I don't say that what is said is not true.

Just imagine you took a 2 pages pamphlet about how to use an LLM and you splitted every sentence into a wannabee "pattern".

▲ soulchild77 3 days ago | parent [-]

I felt the same and I asked Claude about it. The answer made me chuckle:

> There’s definitely a tendency to dress up fairly straightforward concepts in academic-sounding language. “Agentic” is basically “it runs in a loop and decides what to do next.” Sliding window is just “we only look at the last N tokens.” RAG is “we search for stuff and paste it into the prompt.” [...] When you’re trying to differentiate your startup or justify your research budget, “agentic orchestration layer” lands differently than “a script that calls Claude in a loop.“

	▲	spaceman_2020 3 days ago \| parent \| next [-]
		I had someone argue on Twitter recently that they had made an “agent” when all they had really done was use n8n to make a loop that used LLMs and ran on a schedule People are calling if-then cron tasks “agents” now
	▲	greatgib 2 days ago \| parent \| prev [-]
		Now that you say it, I just realize that it might be useful to me one day if I'm a bland useless startup and I try to dress up my pitch with these terms to try to raise investor money...