Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The Agentic AI Handbook: Production-Ready Patterns

nibzard.com

Post reply on HN
Print view View original

131–140 of 151 posts

Re: The Agentic AI Handbook: Production-Ready Patterns

#131

Post by gbnwl »

zuInnp wrote: post #38

Not only is the website layout horrible to read, it also smells like the article was written by AI. My brain just screams "no" when I try to read that.

It’s also just fluff and straight up wrong at parts. This wasn’t checked by a human or at least a human who understands enough to catch inaccuracies. For example for “Plan-then-execute” (which is presented as some sort of novel pattern rather than literally just how Claude Code works right out of the box) it says:

“Plan phase – The LLM generates a fixed sequence of tool calls before seeing any untrusted data

Execution phase – A controller runs that exact sequence. Tool outputs may shape parameters, but cannot change which tools run”

But of course the agent doesn’t plan an exact fixed sequence of tool calls and rigidly stick to it, as it’s going to respond to the outputs which can’t be known ahead of time. Anyone who’s watched Claude work has seen this literally every day.

This is just more slop making it to the top of HN because people out of the loop want to catch up on agents and bookmark any source that seems promising.

Re: The Agentic AI Handbook: Production-Ready Patterns

#132

Post by photios »

alkonaut wrote: post #100
photios wrote: post #56

Earlier quoted context omitted.

Copilot's agent mode is a disaster. Use better tools: try Claude Code or OpenCode (my favorite). It's a new ecosystem with its own (atrocious!) jargon that you need to learn. The good news is that it's not hard to do so. It's not as complex or revolutionary as everyone makes it look like. Everything boils down to techniques and frameworks of collecting context/prompt before handing it over to the model.

Sadly we have some partnership meaning it's Copilot or nothing.

I feel your pain. I used to work for a bank and the security team only approved Copilot use.

OpenCode can use Copilot natively: https://opencode.ai/docs/providers/#github-copilot

I got Claude Code running with Copilot APIs via the LiteLLM proxy, but it was a pain in the butt. Just use OpenCode.

Re: The Agentic AI Handbook: Production-Ready Patterns

#133

Post by ozim »

mellosouls wrote: post #86

Not wanting to be a gatekeeper, but the author appears to be a "AI Growth Innovator" or some-such-I-don't-know-what rather than an actual engineer who has been ramping up on AI use to see what works in production: https://www.nibzard.com/about Scaled GitHub stars to 20,000+ Built engaged communities across platforms (2.8K X, 5.4K LinkedIn, 700+ YouTube) etc, etc. No doubt impressive to marketing types but maybe a pin…

I was hoping that's some sitting in the basement playing hard with LLMs dude post.

But that's a dead give away he is just scaling GitHub stars not doing actual research.

Re: The Agentic AI Handbook: Production-Ready Patterns

#134

Post by ikidd »

alkonaut wrote: post #97
embedding-shape wrote: post #26

Earlier quoted context omitted.

> I never had any luck integrating agents What exactly do you mean with "integrating agents" and what did you try? The simplest (and what I do) is not "integrating them" anywhere, but just replace the "copy-paste code + write prompt + copy output to code" with "write prompt > agent reads code > agent changes code > I review and accept/reject". Not really "integration" as much as just a workflow change.

I installed the copilot extension in my IDE, and switched on Agent mode. I don't really get how the workflow is supposed to work, but I think it's mostly due to how the tool is made. It has like some sort of "change stack" similar to git commits/staging but which keeps conflicting with anything I manually edit. Perhaps it's just this particular implementation (Copilot integration in VS) which is bad, and others are b…

Copilot is a dumpster fire and I can understand why you're down on agents from that experience.

Splurge on the $20 for Cursor, and install their IDE. Start with a simple project, more because it helps you see how it works than because Cursor can't handle more. Give it specific instruction and not too big a problem at one time so you can tailor the prompt. If it's niche, consider changing the model to Opus4.5 long enough for it to get a handle on the codebase. Use the Plan mode to start, adjust the plan, then let it god. Every time it makes changes it can be reverted to the state at previous prompts. Use git liberally.

I'm just a dumb farmer who quit programming 20 years ago, and I use it to build stuff that works IRL for my operation constantly. A dev should be able to wrap their head around it.

Re: The Agentic AI Handbook: Production-Ready Patterns

#135

Post by ikidd »

embedding-shape wrote: post #106
alkonaut wrote: post #97

Earlier quoted context omitted.

I installed the copilot extension in my IDE, and switched on Agent mode. I don't really get how the workflow is supposed to work, but I think it's mostly due to how the tool is made. It has like some sort of "change stack" similar to git commits/staging but which keeps conflicting with anything I manually edit. Perhaps it's just this particular implementation (Copilot integration in VS) which is bad, and others are b…

Hm, yeah maybe. I've tried Cursor once, but the entire experience was so horrible, and it was really hard to know what's going on. The workflow I have right now, is something like what I put before, and I do it with Codex and Claude Code, both work the same. Maybe try out one of those, if you're comfortable with the terminal? It basically opens up a terminal UI, can read current files, you enter a prompt, wait, then…

If you're dumping the context every prompt, that might be why you're not happy with the results of Cursor. I can run a dozen or two prompts before the context gets polluted enough that it's worth compacting. If you clear it's context every time, it's not going to get a holistic enough view of the problem to deliver a good feature.

That's been my experience. You have to work them up to the big ask.

Re: The Agentic AI Handbook: Production-Ready Patterns

#136

Post by Macha »

dist-epoch wrote: post #90
Macha wrote: post #65

Earlier quoted context omitted.

There isn't a bunch of managers metaphorically asking people if they're using vim enough, and not so many blog posts proclaiming vim as the only future for building software

You must be new here. "I use vim between", "you don't use vim, you use Visual Studio, your opinion doesn't count" is a thing in programming circles.

Internet commenters, sure.

It never broke into the workplace like measuring AI use among your employees. Nobody's asked me about how I've used vim keybinds to improve the company's growth in a performance review.

Re: The Agentic AI Handbook: Production-Ready Patterns

#137

Post by TeMPOraL »

darkwater wrote: post #80
franze wrote: post #52

Earlier quoted context omitted.

I am on the other side, I have given the complete control of my computer to Claude Code - Yolo Mode. Sudo. It just works. My servers run the same. I SSH into Claude Code there and let them do whatever work they need to do. So my 2 cents. Use Claude Code. In Yolo mode. Use it. Learn with it. Whenever I post something like this I get a lot of downvots. But well ... end of 2026 we will not use computer the way we use th…

Claude Code and agents are the hot new hammer, and they are cool, I use CC and like it for many things, but currently they suffer from the "hot new hammer" hype so people tend to think everything is a nail the LLM can handle. But you still need a screwdriver for screws, even if you can hammer them in.

That "hot new hammer" hype is a good thing given general enough tool, and LLMs very much are that. We did the same with smartphones, the Internet, personal computers, and even electricity.

Some 150 years ago, humanity collectively decided to try and redo everything but with electricity. In some cases, it was a clear success - e.g. lights. It enabled further progress - see e.g. computers, MRI machines, etc. In other cases, it was a failure - see e.g. cars, which still rely on ICEs despite electric cars being first, because until recently batteries just were not there. And then, in many cases the adoption was partial - see e.g. power tools, which are usually electrical, but in professional / industrial use, there's lots of hydraulic/pressurized air powered variants.

All the above took people trying things out, "throwing shit at the wall to see what sticks". We're at this stage with LLMs now.

Re: The Agentic AI Handbook: Production-Ready Patterns

#138

Post by chewz »

torben-friis wrote: post #60
prettygood wrote: post #40

Earlier quoted context omitted.

I'm so happy someone else says this, because I'm doing exactly the same. I tried to use agent mode in vs code and the output was still bad. You read simple things like: "We use it to write tests". I gave it a very simple repository, said to write tests, and the result wasn't usable at all. Really wonder if I'm doing it wrong.

I’m not particularly proAI but I struggle with the mentality some engineers seem to apply to trying. If you read someone say “I don’t know what’s the big deal with vim, I ran it and pressed some keys and it didn’t write text at all” they’d be mocked for it. But with these tools there seems to be an attitude of “if I don’t get results straight away it’s bad”. Why the difference?

Some people shouldn't just be engineers in the first place, I guess.

Re: The Agentic AI Handbook: Production-Ready Patterns

#139

Post by galaxyLogic »

0xbadcafebee wrote: post #41

You should definitely read the whole thing, but tl;dr - Generate a stable sequence of steps (a plan), then carry it out. Prevents malicious or unintended tool actions from altering the strategy mid-execution and improves reliability on complex tasks. - Provide a clear goal and toolset. Let the agent determine the orchestration. Increases flexibility and scalability of autonomous workflows. - Have the agent generate,…

Could I ask the AI to create me a set of template-files as described by you above? Or if there is an example set of template files somewhere then ask the AI to do its thing based on those? Or ask the AI to create me such a set of template files for it to work on?

I mean why do I need to read from HN what to do, if AI is so knowledgable and even agentic?

Re: The Agentic AI Handbook: Production-Ready Patterns

#140

Post by galaxyLogic »

Nekobai wrote: post #129
galaxyLogic wrote: post #70

Earlier quoted context omitted.

Well one could say that since it's AI, AI should be able to tell us what we're doing wrong. No? AI is supposed to make our work easier.

Certainly, every tool is supposed to make our work easier or more productive, but that doesn't mean that every tool is intuitive or easy to learn to use effectively or even to use it at all.

Certainly, but aren't AI tools supposed to be intuitive and easy to use because we can communicate with them in natural language?

With VIM or Emacs I am supposed to know what Ctrl-X does. But with AI tools (ideally) I should be able to ask AI (in English) to edit the document for me?

Maybe the reason we can't do it that way is that, "We're not there yet"?

Post reply on HN