Skip to main content
Generated Image February26,2026 5 04PM Jpg
The time of a truly autonomous General Developer Agent is here. Remember the series Silicon Valley? Where Gilfoyle’s Anton AI literally took over the company’s entire codebase and ended up deleting stuff or ordering huge amounts of meat? I think the time is already here, and somewhere in the world, somebody has already built it. I am doing this interesting exercise while I am writing this piece. The main answer I am looking for is — “In an ideal world, if I had the chance to create the best developer ever, what are the skills, qualities and best practices I would want the developer to have?” I have spent my last eight years of my life coding. I have tried multiple roles like being a founder or being a PM. In all of those roles, I have found one thing in common: if you know coding irrespective of whichever role you are, you get this magical ability to visualise systems in a way that nobody else can. For the rest of the world, all of these systems might sound gibberish, but as a developer, you know these systems are running the world, and you feel super proud of something you have built which has an insane level of engineering behind it. This is about to change. If you think honestly, you would realise that developing a product is such a mechanical piece of work, and somehow we get attached to it emotionally. But do you really think that is where you want to spend the rest of your life? That is what can give you an insane amount of wealth? For most people, it won’t. For that 0.1% of exceptional devs, we still need you, and I think you are enough to handle all the things which need dev work today. But for the remaining 99.9% of the people, I think it’s time to change our approach. AI has officially started moving the human race forward once again. I will talk about the approach in a different blog, but let’s come back to our main goal of building a truly autonomous General Developer Agent.

Workflow ≠ Agentic

First, let me break down why I am talking about General Developer Agent and especially emphasising on the word General. Developers are human at the end of the day. So when it comes to creating a truly autonomous developer agent, there is a high chance of ending up creating a workflow-driven agent rather than an agentic one. I made this mistake. When it comes to reliability, this works, but this does not really challenge the motto of “Building for the next model”.
Don’t create a workflow. As humans, we don’t work on workflows. If you are given the same tasks every 1-2 months, almost 100% of the time, you will do something differently every time you take up that task.
There is no reason to think that agents can’t do the same. Let’s remind ourselves that with every individual experiment like this, our goal should be building for the next model. Now, coming to my thought of how being a developer can make you better at any job. My entire purpose of doing this is to offload any kind of dev work to the agent and focus on more important things like product, growth, design, etc. Hence, I am going to design this developer in such a way that it can technically become a digital developer clone of me.

The Values of a Great Developer

As a developer, I have grown over the years to have some values, and those values are:
  • Quality over speed
  • Thinking of multiple use cases before building
  • Thinking of multiple edge cases as well
  • Trying to write down the thoughts
  • Finding the RCA
  • Trying to explore multiple possible solutions
  • Writing test cases
  • Writing comments
  • Writing tech docs
Now, these are things that come to mind when I think of an ideal world. I would rather spend most of my time doing all of these before starting to code. But let’s be real, hardly ever do we get to tick all the points due to deadlines. AI already has taken care of a lot of the parts like test cases, comments, and tech docs reliably. But now is the time I think each and every one of these values can be reliably followed using a truly autonomous General Developer Agent.

The Skills AI Already Has

Next is the skills that we want the best developer to have. Certain skills are required to be able to take care of all the requirements which come with infinite possibilities. For human learning, every language, every best practice, or tackling every requirement is just impossible. But not for AI.
  • AI already knows all the languages in the world.
  • AI already has an understanding of best practices, thanks to some of the OGs in the dev world for writing those insightful blogs.
  • AI can navigate computers today. There is definitely scope for improvement, but at least it can run terminal reliably.
  • AI already can browse the internet both in headless mode and in headful mode. Yes, it is slow, but I think it is getting better every day.
I think these are the four skills or knowledge that can let you cover almost 90-95% of the tasks you want to give it. I am personally running such an agent for shipping features for the last couple of days, and my days have not looked better ever.

What Actually Makes a Developer Great

But above all of these, there are certain qualities which make a developer truly great. These are:
  • Finding the root cause reliably
  • Context aware systems thinking and the ability to design it
  • Project specific memory and the ability to learn from its mistakes
  • Knowing what not to build means finding an existing solution, library, or managed service
  • Knowing when “good enough” is actually “good enough”
While we expect these qualities from every developer that every company hires, these actually differentiate the best developers from the set of average ones.

So Here’s What I’m After

I want to build the best developer in the world, and this is going to be an iterating project I am going after, and it might take days. I know in this world, days are like months. But I am consciously going to take days. Not going to spend my everyday building this, but I would rather like to find and jot down all the use cases I can think of that can make my life with nearly 0 dev work. This unlocks something super important. As developers, there is a tendency to jump into the build mode without even starting to think. Most of the time, this ideology distracts the individual from the core problem that he or she is trying to solve. That’s why you will find most of the visionary founders are not necessarily developer-first.
Everyone should be completely free from the thought of how to build things. Every founder, product manager, and designer needs to start focusing on the problem they are trying to solve and become completely free from the thought of technical limitations.
I have already created pieces of it. Some proactive agents are always connected to my tools, and a CLI tool that uses Claude Code to work on my project from a Slack channel. I have also tried OpenClaw, but it consumes too many tokens. So all in all, this is a product which actually can evolve every day and will end up making my days easier over time, and probably I will pick up farming or living on mountains in no time.