The word cost is mentioned only twice in the entire article, lol
The Agentic AI Handbook: Production-Ready Patterns
81–90 of 151 posts
Re: The Agentic AI Handbook: Production-Ready Patterns
#82I sometimes feel like the cognitive cost of agentic coding is so much higher than a skilled human. There is so much more bootstrap and handling process around making sure agents don't go off the rails (they will), or that they will adhere to their goals (they won't). And in my experience fixing issues downstream takes more effort than solving the issue at the root. The pipe dream of agents handling Github Issue -> Pu…
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?
Re: The Agentic AI Handbook: Production-Ready Patterns
#83Earlier 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?
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
I’d argue that, if we accept that AI is relevant enough to at least be worth checking, then dismissing it with minimal effort is just as bad as mindlessly hyping the tech.
Re: The Agentic AI Handbook: Production-Ready Patterns
#84Earlier 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?
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.
What you are doing wrong in respect to what? If you ask for A, how would any system know that you actually wanted to ask for B?
Re: The Agentic AI Handbook: Production-Ready Patterns
#85Earlier quoted context omitted.
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.
This is something that continues to surprise me. LLMs are extremely flexible and already come prepackaged with a lot of "knowledge", you don't need to dump hundreds of lines of text to explain to it what good software development practices are. I suspect these frameworks/patterns just fill up the context with unecessary junk.
I think avoiding filling context up with too much pattern information, is partially where agent skills are coming from, with the idea there being that each skill has a set of triggers, and the main body of the skill is only loaded into context, if that trigger is hit.
You could still overload with too many skills but it helps at least.
Re: The Agentic AI Handbook: Production-Ready Patterns
#86Not 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:
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 pinch of salt required for using AI Agents in production.
Re: The Agentic AI Handbook: Production-Ready Patterns
#87Not 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.
Seems like a reasonable feeling to have. Anything that's not worth writing is not worth reading imo.
Eh, you're going too far with that IMO.
The other day we were discussing a new core architecture for a Microservice we were meant to split out of a "larger" Microservice so that separate teams could maintain each part.
Instead of just discussing it entirely without any basis, I instead made a quick prototype via explicit prompts telling the LLM exactly what to create, where etc.
Finally, I asked it to go through the implementation and create a wiki page, concatting the code and outlining in 1-4 sentences above each "file" excerpt what the goal for the file is.
In the end, I went through it to double-check if it held up from my intentions - which it did and thus didn't change anything
Now we could all discuss the pros and cons of that architecture while going through it, and the intro sentence gave enough context to each code excerpt to improve understanding/reduce mental load as necessary context was added to each segment.
I would not have been able to allot that time to do all this without an LLM - especially the summarization to 1-3 sentences, so I'll have to disagree when you state this generally.
Though I definitely agree that a blog article like this isn't worth reading if the author couldn't even be arsed to write it themselves.
Re: The Agentic AI Handbook: Production-Ready Patterns
#88So it begins, Design Patterns and Agile/Scrum snake oil of modern times.
No no. We promise this solution has a totally different name.
In the spirit of the article, I asked chatgpt to suggest names.
One of the better ones were "Unified LLM Interaction Model (ULIM)". You read it here first...
Re: The Agentic AI Handbook: Production-Ready Patterns
#89Am I the only one with scrolling issues in Firefox on this website?
It literally gets "stuck" and becomes un-scrollable.
Re: The Agentic AI Handbook: Production-Ready Patterns
#90Earlier 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?
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.