Live data from Hacker News

The Agentic AI Handbook: Production-Ready Patterns

nibzard.com

101–110 of 151 posts

Re: The Agentic AI Handbook: Production-Ready Patterns

#101

All of this might as well be greek to me. I use ChatGPT and copy paste code snippets. Which was bleeding edge a year or two ago, and now it feels like banging rocks together when reading these types of articles. I never had any luck integrating agents, MCP, using tools etc. Like if I'm not ready to jump on some AI-spiced up special IDE, am I then going to just be left banging rocks together? It feels like some of the…

I feel like just use claude code. That is it. Use it you get the feel for it. Everyone is over complicating. It is like learning to code itself. You need flight hours.

I'm stuck with the Copilot tools. Again, I don't think this is a problem with the models but with the tooling. I can't switch to claude code (for work, that is) and while I don't mind using more command line tools I don't want to run multiple IDE's.

But it's good to hear that it's not me being completely dumb, it's Copilot Agent Mode tooling that is?

Re: The Agentic AI Handbook: Production-Ready Patterns

#102
post #52

All of this might as well be greek to me. I use ChatGPT and copy paste code snippets. Which was bleeding edge a year or two ago, and now it feels like banging rocks together when reading these types of articles. I never had any luck integrating agents, MCP, using tools etc. Like if I'm not ready to jump on some AI-spiced up special IDE, am I then going to just be left banging rocks together? It feels like some of the…

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…

[dead]

Re: The Agentic AI Handbook: Production-Ready Patterns

#103
The emergence of this kind of thing has been so surprising to me. The exact same sort of person that managed to bottleneck themselves and obliterate signal-to-noise ratios at every company they work for with endless obsession over the trivial minutiae of the systems they are working with have found a way to do it with LLMs, too, which I would have assumed would have been the death of this kind of busywork

Re: The Agentic AI Handbook: Production-Ready Patterns

#104

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…

Make sure you’re clicking “Keep” to “approve” the changes. It’s annoying but I don’t think there is a way around having to do that. Then if you manually edit something, you can mention it in your next chat message, e.g., “I made a few changes to . ”

Re: The Agentic AI Handbook: Production-Ready Patterns

#105
post #14

So it begins, Design Patterns and Agile/Scrum snake oil of modern times.

No dude, you just don't get it, if you shout at the ai that YOU HAVE SUPERPOWERS GO READ YOUR SUPERPOWERS AT ..., then give it skills to write new skills, and then sprinkle anti grader reward hacking grader design.md with a bit of proactive agent state externalization (UPDATED), and then emotionally abuse it in the prompt, it's going to replace programmers and cure cancer yesterday. This is progress.

[flagged]

Re: The Agentic AI Handbook: Production-Ready Patterns

#106

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…

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 can review the results with git or whatever VCS you use.

But I'm also never "vibe-coding", I'm reviewing every single line, and mercilessly ask the agent to refactor whenever the code isn't up to my standards. Also restart the agent after each prompt finished, as they get really dumb as soon as context is used more than 20% of their "max".

Re: The Agentic AI Handbook: Production-Ready Patterns

#107

Earlier quoted context omitted.

It can definitely feel like that right now but I think a big part of that is us learning to harness it. That’s why resources like this are so valuable. There’s always going to be pain at the start.

I've seen this "we're still learning" argument for at least 6 months now and I get it and even agree with it. However at which point do we start to question how much is it part of a learning curve and how much is just limitations of the models/software?

[flagged]

Re: The Agentic AI Handbook: Production-Ready Patterns

#108
post #99

Earlier quoted context omitted.

Yeah if you've not used codex/agent tooling yet it's a paradigm shift in the way of working, and once you get it it's very very difficult to go back to the copy-pasta technique. There's obviously a whole heap of hype to cut through here, but there is real value to be had. For example yesterday I had a bug where my embedded device was hard crashing when I called reset. We narrowed it down to the tool we used to flash…

- We narrowed it down to the tool we used to flash the code. - I downloaded the repository, jumped into codex, explained the symptoms and it found and fixed the bug in less than ten minutes. Change the second step to: - I downloaded the repository, explained the symptoms, copied the relevant files into Claude Web and 10 minutes later it had provided me with the solution to the bug. Now I definitely see the ergonomic…

I agree with your statement and perhaps my example is bad/too specific in this case.

Once I started working this way however, I found myself starting to adapt to it.

It's not unusual now to find myself with at least a couple of simultaneous coding sessions, which I couldn't see myself doing with the friction that using Claude Web/Codex web provides.

I also entirely agree that there's going to be a lot of innovation here.

IDEs imo will change to become increasingly focused on reading/reviewing code rather than writing, and in fact might look entirely different.

Re: The Agentic AI Handbook: Production-Ready Patterns

#109
It's unbelievable how productive AI has made me. With the release of the latest Claude, I'm now able to achieve 100x more than I could have without it.

In one week, I fine-tuned https://github.com/kstenerud/bonjson/ for maximum decoding efficiency and:

* Had Claude do a go version (https://github.com/kstenerud/go-bonjson), which outperforms the JSON codec.

* Had Claude do a Rust version (https://github.com/kstenerud/rs-bonjson), which outperforms the JSON codec.

* Had Claude do a Swift version (https://github.com/kstenerud/swift-bonjson), which outperforms the JSON codec (although this one took some time due to the Codable, Encoder, Decoder interfaces).

* Have Claude doing a Python version with Rust underpinnings (making this fast is proving challenging)

* Have Claude doing a Jackson version (in progress, seems to be not too bad)

In ONE week.

This would have taken me a year otherwise, getting the base library going, getting a test runner going for the universal tests, figuring out how good the SIMD support is and what intrinsics I can use, what's the best tooling for hot path analysis, trying various approaches, etc etc. x5.

Now all I do is give Claude a prompt, a spec, and some hand-holding for the optimization phase (admittedly, it starts off at 10x slower, so you have to watch the algorithms it uses). But it's head-and-shoulders above what I could do in the last iteration of Claude.

I can experiment super quickly: Try caching previously encountered keys and show me the performance change. 5 mins, done. Would take me a LOT longer to retool the code just for a quick test. Experiments are dirt cheap now.

The biggest bottleneck right now is that I keep hitting my token limits 1-2 hours before each reset ;-)

Re: The Agentic AI Handbook: Production-Ready Patterns

#110
post #22

If you are interested here is a list of actual agentic patterns - https://go.cbk.ai/patterns

You could also disclose you work there. Because as soon as I started reading the patterns I realized this was bogus and one could only recommend this because of personal stakes.

Bogus in what way?
Post reply on HN