An architect standing before a large system architecture display
ORNET
2025 → 2028

From
Developer
to
AI
Architect.

A personal journey into the age of intelligent systems.

scroll
A developer working alone at night surrounded by monitors
2025
Chapter 01

The Builder

I was building everything myself.

Every feature. Every bug. Every decision.

Day by day...

The problem wasn't coding.

The problem was scale.

A developer working with an AI support panel inside his normal development tools
2026 · H1
Chapter 02

The AI‑Supported
Developer

Then I discovered something:

intelligence could be multiplied.

AI wasn't the replacement.

It was the multiplier.

A developer orchestrating a team of specialized AI agents
2026 · H2
Chapter 03

The
Orchestrator

I stopped doing everything myself.

First, I started using agents.

Then I learned how to orchestrate them.

AI became a team.

My team.

An office at night where AI agents keep working
The Forge2027 · Chapter 04

While I slept…
the system kept building.

Not automation.

Orchestration.

22:00 · Night Run Active02:17
12
Tasks
2,847
Lines
94
Tests
3
PRs
The architect reviewing system orchestration at sunrise
2028
Chapter 05

The
Architect

I no longer build every solution.

I design the systems that create them.

The future doesn't belong to those who automate everything.

It belongs to those who keep intelligent systems accountable.

A quiet sunrise with a man standing calmly in the distance

I thought AI would replace developers.

I was wrong.

It transformed them.

First, I was a developer.

Then my work moved, step by step,
toward architecture built with AI.

My personal path may still lead
somewhere entirely different.

Right now, cloud architecture is becoming
the next part of that path.

And wherever AI creates real value,
I will bring it into the system.

The future will change.
And so will I.

Oliver

What will you become?

AI Architecture

Designing intelligent systems that stay accountable.

ORNET is the personal website of Oliver Röschner. It documents his path from software development toward AI architecture, agent orchestration and cloud-native systems.

His work focuses on intelligent software systems where autonomy needs structure: clear responsibilities, guardrails, audit trails, human approval and architecture that can evolve as technology changes.

AI architecturecloud architectureagent orchestrationsoftware architectureAI engineeringguardrailshuman approval workflows

What does an AI Architect do?

An AI Architect designs software systems that use AI responsibly: the workflows, agent roles, data boundaries, approval points, observability and fallback paths that keep intelligent systems useful and accountable.

How does AI change software development?

AI shifts software development from only writing code toward designing systems that can research, generate, review, test and document work under human direction.

What is agent orchestration?

Agent orchestration is the coordination of specialized AI agents and tools so they work toward a controlled outcome instead of acting as isolated automation scripts.

How does cloud architecture fit into AI systems?

Cloud architecture provides the foundation for scalable, observable and secure AI systems: deployment, identity, data boundaries, monitoring, cost control and reliable integration with existing software.

Why are guardrails important in AI engineering?

Guardrails define what an AI-assisted system may do, what it must explain, where it must stop and when a human must approve the next step.

What is the difference between automation and orchestration?

Automation executes predefined tasks. Orchestration coordinates people, AI agents, tools and policies so complex work can happen with traceability and control.