Tobias Glöckler Agentic Engineer

Agentic Coding: How AI Is Changing Software Engineering

3 min read AI
Illustration showing the concept of agentic coding

A deep dive into how agentic AI tools are transforming the way we write, debug, and ship software — and what it means for the future of engineering.

What Is Agentic Coding?

Agentic coding refers to the use of AI systems that can autonomously plan, write, and iterate on code with minimal human intervention. Unlike traditional code completion tools that suggest the next line, agentic systems understand the full context of what you’re building and can execute multi-step tasks.

Think of it as the difference between a spell-checker and a co-author. One fixes typos; the other understands your narrative and helps you write entire chapters.

Why It Matters Now

The shift from assistive AI to agentic AI in software engineering is happening faster than most people realize. Here’s what’s driving it:

  • Context windows are growing — modern models can process entire codebases, not just single files
  • Tool use is maturing — AI agents can run tests, read docs, and interact with APIs
  • Feedback loops are tightening — agents can verify their own output and self-correct

The best code is the code you don’t have to write. Agentic systems take this further: the best debugging is the debugging you don’t have to do.

How I Use It in My Workflow

As an agentic engineer, I’ve integrated AI tools deeply into my daily workflow. Here’s a typical process:

  1. Define the intent — I describe what I want to build in natural language
  2. Let the agent plan — The AI breaks the task into steps and identifies relevant files
  3. Review and guide — I provide feedback on the approach before execution
  4. Iterate together — The agent implements, I review, we converge on the solution

A Practical Example

Let’s say I need to add a new API endpoint. Instead of manually scaffolding the route, handler, validation, and tests, I describe the requirement:

// The agent generates this from a natural language description
export async function POST({ request }: APIContext) {
  const body = await request.json()
  const validated = schema.parse(body)

  const result = await db.insert(projects).values(validated)

  return new Response(JSON.stringify(result), {
    status: 201,
    headers: { 'Content-Type': 'application/json' },
  })
}

The agent also generates the Zod schema, the database migration, and the test file — all in one pass.

The Human Element

Despite the power of agentic tools, the human element remains critical. AI is excellent at execution but still needs human judgment for:

  • Architecture decisions — choosing the right patterns and trade-offs
  • Product thinking — understanding what users actually need
  • Code review — catching subtle issues that tests miss
  • Security — ensuring the generated code doesn’t introduce vulnerabilities

Looking Ahead

The next wave of agentic coding tools will likely feature:

CapabilityCurrent StateNear Future
Code generationSingle filesFull features across repos
TestingUnit testsIntegration + E2E
DeploymentManualAutomated with rollback
MonitoringNoneSelf-healing systems

The engineers who thrive won’t be those who resist these tools, but those who learn to direct them effectively — like a conductor leading an orchestra rather than playing every instrument.

Getting Started

If you’re new to agentic coding, start small:

  1. Pick a repetitive task in your workflow
  2. Try describing it to an AI agent instead of doing it manually
  3. Compare the output quality and time spent
  4. Gradually expand to more complex tasks

The future of software engineering isn’t about writing more code — it’s about building better systems with less friction.

Share:
Tobias Glöckler

Tobias Glöckler

Agentic Engineer

Building AI automations, custom software, and web products.