Live data from Hacker News

Levels of Agentic Engineering

bassimeledath.com

111–120 of 152 posts

Re: Levels of Agentic Engineering

#111

[dead]

> prioritization and decision frameworks start to matter more.

This is the thing though, prioritization doesn't matter in the same way it used to.

We only needed to prioritize before because engineering was relatively slow and precious resource, so we had to pick and chose what to work on first because it took time.

But now we effectively have a limitless supply of SWEs, so why not do everything on the backlog?

I think the question now is more about sequencing than prioritization. What do we need to do first, before we can do these other things?

But yes generally requirements are still very important. Which features do we need etc.

Re: Levels of Agentic Engineering

#112
post #4

Yegge's list resonated a little more closely with my progression to a clumsy L8. I think eventually 4-8 will be collapsed behind a more capable layer that can handle this stuff on its own, maybe I tinker with MCP settings and granular control to minmax the process, but for the most part I shouldn't have to worry about it any more than I worry about how many threads my compiler is using.

Yep I was also surprised to see MCP & Skills as not only a distinct "level", but so high up.

In my mind, MCP & Skills is inseparable part of chat interfaces for LLMs, not a distinct level.

Re: Levels of Agentic Engineering

#113

As a Level 6, I am feeling like to go back to Level 5. Level 6 helps with fixing bugs, but adding a new feature in a scalable way is not working out for me, I feed bunch of documents and ask it to analyze and come up with a solution. 1. It misses some details from docs when summarizing 2. It misses some details from code and its architecture, especially in multi-repo Java projects (annotations, 100 level inheritance…

Most of the successes, especially online, is rarely about the thing that is built but more about the marketing around it. I don't we can fully automate marketing effectively

Re: Levels of Agentic Engineering

#114

Level 4 is where I see the most interesting design decisions get made, and also where most practitioners take a shortcut that compounds badly later. When the author talks about "codifying" lessons, the instinct for most people is to update the rules file. That works fine for conventions - naming patterns, library preferences, relatively stable stuff. But there's a different category of knowledge that rules files hand…

[dead]

Re: Levels of Agentic Engineering

#118

Level 9: agent managers running agent teams Level 10: agent CEOs overseeing agent managers Level 11: agent board of directors overseeing the agent CEO Level 12: agent superintelligence - single entity doing everything Level 13: agent superagent, agenting agency agentically, in a loop, recursively, mega agent, agentic agent agent agency super AGI agent Level 14: A G E N T

Until we solve agent consumers that become the backstop of the economic engine when we all get unemployed, who are these agents working for?
Post reply on HN