AI can write code, but it cannot take responsibility for the architecture

Will AI become the new god?
Will we all lose our jobs?

My short answer is no.

Not because AI is useless. Quite the opposite. At Webnorth, we use AI every day, and it significantly increases our speed.

But there is a big difference between using AI as a tool and letting AI handle complex development tasks on its own.

In the SWE-bench study from Princeton, AI models were tested on real GitHub issues from open source projects. The tasks required the models to understand an existing codebase and make changes that actually solved the issue. In the original benchmark, even the best-performing model solved only 1.96% of the tasks correctly.

That does not mean AI cannot be used in development.

It means there is a big difference between:

Assisting a developer
Writing isolated code
Understanding architecture, dependencies, and long-term consequences

The last point is the important one.

When AI is used without strong developers behind it, technical debt can build up quickly. The code may look correct in the moment, but still be difficult to maintain, poorly structured, or placed incorrectly in the overall solution.

We never accept code we do not fully understand.

This is not about being skeptical of AI. It is about responsibility.

AI can help with speed, research, suggestions, debugging, and repetitive tasks. But in complex WordPress solutions, humans still need to understand the whole system, make the decisions, and make sure the solution can hold up over time.

AI is a powerful tool.

But it is still a tool, especially when working with enterprise WordPress and high-complexity setups.

Source:
SWE-bench: Can Language Models Resolve Real-World GitHub Issues?