Re:Agentic Patterns
by soulchild77 on Monday January 05, 2026 @01:37AM
(#46495920)
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.“
Re:Agentic Patterns
by spaceman_2020 on Monday January 05, 2026 @02:48AM
(#46496293)
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
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: