Software engineering is often treated as a technical problem. In real systems, many of the hardest challenges are not technical at all.

In integration-heavy environments, complexity comes from ownership, alignment, and decisions made under constraints. This shows up before writing code, while building, and long after systems are in production.

Systems move across teams, responsibilities become unclear, and progress depends on coordination more than implementation.

At the same time, writing code and producing documentation is getting easier. The bottleneck is shifting. Building is faster, but deciding what to build and aligning people around it remains difficult.

This talk looks at how systems become hard to understand, why technically correct solutions are not always the ones shipped, and how knowledge ends up concentrated in a few people.

It is a reflection on software engineering in practice, where understanding and alignment matter as much as code.