Live data from Hacker News

The Agentic AI Handbook: Production-Ready Patterns

nibzard.com

111–120 of 151 posts

Re: The Agentic AI Handbook: Production-Ready Patterns

#111

Earlier quoted context omitted.

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?

I don't understand how to get even bad results. Or any results at all. I'm at a level where I'm going "This can't just be me not having read the manual". I get the same change applied multiple times, the agent having some absurd method of applying changes that conflict with what I say it like some git merge from hell and so on. I can't get it to understand even the simplest of contexts etc. It's not really that the c…

> I'm at a level where I'm going "This can't just be me not having read the manual".

Sure it can, because nobody is reading manuals anymore :).

It's an interesting exercise to try: take your favorite tool you use often (that isn't some recent webshit, devoid of any documentation), find a manual (not a man page), and read it cover to cover. Say, GDB or Emacs or even coreutils. It's surprising just how much powerful features good software tools have, and how much you'll learn in short time, that most software people don't know is possible (or worse, decry as "too much complexity") just because they couldn't be arsed to read some documentation.

> I just can't get past the actual tool use. In fact, I don't think I'm even at the stage where the AI output is even the problem yet.

The tools are a problem because they're new and a moving target. They're both dead simple and somehow complex around the edges. AI, too, is tricky to work, particularly when people aren't used to communicating clearly. There's a lot of surprising problems (such as "absurd method of applying changes") that come from the fact that AI is solving a very broad class of problems, everywhere at the same time, by virtue of being a general tool. Still needs a bit of and-holding if your project/conventions stray away from what's obvious or popular in particular domain. But it's getting easier and easier as months go by.

FWIW, I too haven't developed a proper agentic workflow with CLI tools for myself just yet; depending on the project, I either get stellar results or garbage. But I recognize this is only a matter of time investment: I didn't have much time to set aside and do it properly.

Re: The Agentic AI Handbook: Production-Ready Patterns

#112

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…

Correct. Of the various ways to work, I find the in-IDE chat to be the worst. I rarely use it for anything other than “help me understand this line”.

Try one of the CLIs. That’s the good stuff right now. Claude Code (or similar) in your shell, don’t worry about agentic patterns, skills, MCP, orchestrators, etc etc. Just the CLI is plenty.

Re: The Agentic AI Handbook: Production-Ready Patterns

#113

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 recently pasted an error I found into claude code and asked who broke this. It found the commit and also found that someone else had fixed it in their branch. You should use claude code.

You don’t even need to paste. Connect it to your IDE (which should be as easy as installing the Claude plugin in your IDE and typing `ide` in `code`) and it’ll automatically pull in whatever you have selected.

Re: The Agentic AI Handbook: Production-Ready Patterns

#114

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'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 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 think so. The humans should be writing the spec. The AI can then (try to) make the tests pass.

Re: The Agentic AI Handbook: Production-Ready Patterns

#115
post #99

Earlier quoted context omitted.

- 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 h…

> 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 envy you for that. I'm not there yet. I also notice that actually writing the code helps me think through problems and now I sometimes struggle because you have to formulate problems up front. Still have some brain rewiring to do :)

Re: The Agentic AI Handbook: Production-Ready Patterns

#116

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.

You didn't actually just say "write tests" though right? What was the actual prompt you used? I feel like that matters more than the tooling at this point. I can't really understand letting LLMs decide what to test or not, they seem to completely miss the boat when it comes to testing. Half of them are useless because they duplicate what they test, and the other half doesn't test what they should be testing. So many…

There are a lot of comments on HN and other places breathlessly gushing about agents totally doing everything end to end, so I couldn't blame someone new to this space for naively assuming that agents would be able to handle a well-bounded problem such as test coverage reasonably well.

Re: The Agentic AI Handbook: Production-Ready Patterns

#117

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…

That's so trite, what makes people write such sentences and not feel embarrassed? I remember when bragging so callously about arbitrary stuff would make you seem off-putting, what happened with that? Today it seems like everyone is bragging about what they do more than actually doing, and others seem fine with this, just part of "the hustle", where did we go wrong?

the sell outs took over.

Re: The Agentic AI Handbook: Production-Ready Patterns

#118

I’d rather just read the prompt that this article was generated from.

That's like saying you'd rather listen to someone ask a question than read a chapter of a textbook. About 99% of the blogs [written by humans] that reach HN's front page are fundamentally incorrect. It's mostly hot takes by confident neophytes. If it's AI-written, it actually comes close to factual. The thing you don't like is usually right, the thing you like is usually wrong. And that's fine if you'd rather read fi…

> If it's AI-written, it actually comes close to factual.

I am ceaselessly fascinated by how we can all live in the same world yet seemingly inhabit such vastly different realities.

Re: The Agentic AI Handbook: Production-Ready Patterns

#119

Earlier quoted context omitted.

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 h…

> 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 envy you for that. I'm not there yet. I also notice that actually writing the code helps me think through problems and now I sometimes struggle because you have to formulate problems up front. Still have some brain rewiring to do…

I think DHH said it best recently when he stated

"I can literally feel competence draining out of my fingers"

Re: The Agentic AI Handbook: Production-Ready Patterns

#120

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'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.

“Write tests“ may not be enough; provide it with a test harness, and instruct it to “write tests until they pass “. Next would be “your feature isn’t complete without N% coverage”. These require the ‘agentic’ piece, which is at its simplest some prompts run in a loop until an exit condition is met.
Post reply on HN