About Systems

Over decades of industry development, a large body of knowledge has been accumulated about building software systems. There are patterns, practices, and approaches that work. But each system remains unique, with its own context and challenges.

When you work with real systems, you quickly realize: most of the time you don’t start with a clean slate. You start with history, compromises, half-implemented ideas, and changing priorities. And that’s normal.

A New Era of Complexity

With the emergence of AI agents, system complexity is growing exponentially. Now we’re dealing not just with deterministic algorithms, but with autonomous agents that make decisions based on probabilities and context. This changes everything: from testing approaches to monitoring and debugging methods.

Systems are becoming more dynamic and unpredictable. Classical architecture patterns remain important, but now they need to be complemented with new approaches to managing uncertainty and observing agent behavior.

Good architecture starts with understanding context, not applying ready-made solutions. And today this context includes working with AI agents and managing exponentially growing complexity.

Latest Posts

Featured image of post Structural and Behavioral Architecture: Graph-Based Approach to Complexity Control

Structural and Behavioral Architecture: Graph-Based Approach to Complexity Control

AI agents generate code quickly but often create architectural chaos. After two weeks of vibe-coding, the project turned into an unmaintainable mess. It became clear: a formal architecture model is needed. This article shows how to automatically build two types of architectural graphs: structural (from source code via AST) and behavioral (from acceptance test traces). In future articles, I'll cover architecture validation based on these graphs.

Featured image of post Working with Chaos in Architecture

Working with Chaos in Architecture

Most of the time you work not with a clean slate, but with history, compromises, and unfinished ideas. At first, it seems messy. But over time, you understand something important: clarity isn't given — it's created. Sharing experience working with chaotic architectures and how to learn to find patterns where at first glance there's only chaos.