In my journey as a web developer, I always felt comfortable studying, practicing, and coding. It was a familiar cycle: get frustrated with documentation, struggle with code that didn't work, and try to find the solution in the official docs or through our best friend, Stack Overflow.
But all of that changed for me in 2025. And if you are reading this, you probably know why.
We no longer need to be stuck in that endless loop, and it's all thanks to AI. When ChatGPT exploded onto the scene in 2022, we all started seeing this tool as something that would change the way we work. And boy, has it changed it.
Right now, such a dependency on Artificial Intelligence Models has been created that many of us don't see ourselves working or doing our day-to-day tasks without them. Honestly, we shouldn't even consider stopping.
But why do I say everything changed for me in 2025?
AI models have evolved in such a way that, right now, they possibly code 5x better than I do. They know more languages and more syntax, and they have seen more code than I will see in 10 lifetimes.
Simply put, instead of worrying about whether AI is going to take my job, what I have been doing is adopting it into my development and creation process.
At first, like many others, I thought AI was going to replace us—many CEOs of big companies have said so. But the reality, in my opinion, is different: if we don't adopt these tools, we WILL be left without a job.
Starting in 2026, the bar to measure our efficiency as developers is different. It is much higher, and this is all thanks to AI Agents.
The Rise of Agents and MCP
The most prominent case right now is Claude Code, a terminal tool that allows you to integrate with Anthropic's AI models. You can not only develop with it but also perform any type of task and automate it. Agents take AI models to the next level, allowing for orchestration and well-planned work.
Another interesting element—which I've discussed before on my YouTube channel—is the MCP (Model Context Protocol). These are essentially tools that allow us to access functionalities that AI models cannot reach due to their closed design. For example, having access to a Database or a document in the cloud. The examples of what can be done with MCP are infinite; think of them as "plugins" for AI Models.
Add to this the ability for agents to specialize: you can have agents for different types of tasks that understand how to outline plans and implement them.
My Current Stack
Currently, I am using paid tools that have saved me countless hours in my creative and productive process:
✅ ChatGPT Pro
✅ Eleven Labs (for audio/content creation)
✅ Github Copilot Pro
So far, I must say that I don't feel like I'm leveraging the full potential of AI. I feel like I'm only at 20-40% of what AI can actually do for me. My goal for 2026 is to change the way I use it.
The Hardest Question
With all this in mind, how realistic is it for us to delegate the development process to AI? Many questions arise here, but the hardest one for me to answer—and one I haven't been clear on until now—is:
What percentage of the development process should we delegate to AI?
Many reading this might feel they can answer that question. But right now, I don't think we have all the arguments to do so.
Two years ago, I said the AI usage process should just be "you writing and AI autocompleting." That was a total fantasy that lasted only a few months until AI could plan for itself, code generation models improved massively, and the famous "Vibe Coding" emerged.
The moment Agents came into action with all these capabilities, my ideal regarding AI usage collapsed. I realized what AI could do and how wrong I was.
I don't feel capable yet of telling you exactly what our day-to-day life as programmers should look like. However, I do believe that AI is not going to replace us for the moment. And I say "for the moment" because, just as I thought one thing 2 years ago, we don't know what will happen in the next 2.
We'll see how we fare in 2028.
Top comments (0)