Complex
How is it better than a basic Python script and a cron job?
For all the buzz surrounding them, AI agents are simply another form of automation that can perform tasks using the tools you've provided. Think of them as smart macros that make decisions and go beyond simple if/then rules to handle edge cases in input data. Fortunately, it's easy enough to code your own agents and below we'll …
Ehh, sometimes a node-based editor is much easier to use and understand for most people.
It's easier to create a new flow in a system that is already set up in test/prod environments, instead of having to get approval for your script/system from whatever old, disgruntled bastard up in their ivory chair screaming "NO! SECURITY!". Sure, it does become a hindrance when you start doing complex stuff, but then you're looking at someone who should start working on a lower level language.
Node-based editors are higher-level "languages" and while they are very walled-in, it can allow the experts to be working on other things, knowing the users won't be able to do much, if any, damage.
and my brain went into a fog looking at all of those little boxes.
I guess after reading and writing code for 45+ years my parsing skills are text based and I am now an "ok boomer" grandad unable to get hip with the vibe, daddy-o.
You can wrench C/C++,vi, ksh, awk, sed, cut, paste, sort, regex, find, etc from my cold, dead hands...OK, Zoomer?
Bluck
Yeah, I guess it's that "point, click, drag, and drop" visual editor and IDE approach to development, that can lower barrier to entry at first, but also get in the way when folks become experienced. Certainly the JSON for even a simple agent flow ends up complicated due to UI element specifiers like "width" "height" "position" "backgroundColor" and the likes which are not needed for the flow's function iiuc.
It'd probably pay to have a parallel purely scripting approach to designing flows that omits the visual stuff and focuses on what components are used, what they connect to, and how they interact ... then run that from the CLI. Entry-level Hands-Ons would focus on using the visual IDE and advanced ones would cover the scripting equivalent(?).
Not a programmer or a software engineer?. I clearly managed to fool many employers over the years cause these are titles I held (at least early on in my career) and my degree majored in software development.
So I ain't a programmer or a software engineer in your opinion because I don't play while little boxes on a object drag and drop screen?. Interesting theory.
Of course, when I first started programming in 1977 we used flow chart templates to map out process flow and I still did this all the way until I retired (albeit in software that ***checks notes*** used a object drag and drop screen!!!!).
Thus I actually designed my software logic PRIOR to coding and updated the process diagram as needed. And then I would fill in the little boxes with code and not let some bullshit generator do it for me (i.e. I can actually design and code software).
But of all that fails to convince you, my Dad is bigger than your Dad.
Bluck
having to write (and indent) Python... yeah - everything is better :P
but in a more serious note - yes, code is better and what not but its so much better that quite often it's recommended to draw system design and flows using... boxes, from which then code is created al there's that ;)
This looks like the having the basis for a wizard, so users will simply follow the prompts. The catch is whether the output is so constrained that an expert user can’t modify/tune the output or not (think of an Excel chart wizard where the wizard enables you to get a chart out and then you can go into the chart and adjust formula and formats.
Expect there will be many who think AI is just writing a simple prompt and “magic will happen” will find the level of thinking required to actually apply AI to anything useful an eye opener and a little disappointing.
For the past 40 years I have been reading press releases that promised that non-programmers could code just by connecting boxes.
For about 20 years, they have promised that non-programmers could configure workflows the same way.
And now they promise that non-programmers can configure something something agent something.
I expect it to end in tears.
... 'Become Fluent in Japanese in a Week' etc.
It is just automation, a few steps up from a macro, The Quill or HyperCard. But I'm not convinced that it is better than simply doing stuff yourself. Perhaps that is because I can do the things I need to, quickly enough and accurately enough. I suppose agents are designed for people who cannot do things themselves, or want a short cut. In that case, it could be empowering or it could be a recipe for disaster.
Computers were helpful because they did things more quickly, more neatly, on your machine, and were accurate. I'm not sure this can yet tick all those boxes. It may never be able to. There may be a glass ceiling on accuracy/security.
Nevertheless, it is a good article.
Yet again the same problem gets solved in the same way !!!
1. The people who 'code' don't understand the business 'like I do' !!!
2. I don't know how to code and cannot explain the business to someone else.
3. I know, lets use a 'magic' application that allows me to write code !!!
4. It even has boxes and lines to join everything up !!!
5. This is good ... BUT it does not allow me to do 'these things' ???!!!
6. You're a 'coder' ... make this 'magic' application do what I want !!!
7. Wait a minute ... I am spending all my time 'coding' with this 'magic' application.
8. [3 months later] ... maybe I should let people who know how to 'code' do these things !!!
9. Hmmmm!!! ... nice idea but it didn't work as I expected.
10. What happened to the last 6 months of my work life and I still don't have what I wanted !!!
:)