Architectural questions in IT are usually divided into “best practices” and “reinventing the wheel”, yet the boundary between the two stays blurry. The reason is simple: architecture has to evolve together with the company, and the arrival of cross-functional teams is one of the inevitable stages in that evolution.
Architecture for cross-functional teams. Mobius 2025 Spring
How can several teams coexist within a shared codebase without stepping on each other? Where do you find a super-analyst, how do you avoid the tragedy of the commons, and can form determine content? Is there an architectural approach that applies equally to both the backend and mobile applications?
Tragedy of the commons in IT
This time the “silver bullet” is cast from an alloy of formal logic, general relativity, and even quantum field theory, so instead of a dry talk about patterns you will see a cascade of vivid metaphors. Metaphors are handy because they are easy to remember and even easier to rely on in day-to-day work. In this video we meet the Dragon of Complexity. Fighting it is pointless, so we will try to bypass it by riding the waves of information exchange.
