# Software-Development, Team-Topologies, Engineering-Excellence, Organizational-Design

Published articles for Software-Development, Team-Topologies, Engineering-Excellence, Organizational-Design.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Just care less about not being aligned

DevFeed: [Just care less about not being aligned](<https://devfeed.tech/articles/just-care-less-about-not-being-aligned-39922.md>)

Original publisher: [Read original article](<https://mende.io/blog/just-care-less-about-not-being-aligned/>)

Author: tobi@techunicorn.builders (Tobias Mende)

Published: 2021-11-06T10:12:00Z

Content type: opinion

Language: en

Sources: [Tobias Mende](<https://devfeed.tech/sources/tobias-mende.md>)

Topics: [Architecture & Design](<https://devfeed.tech/topics/architecture-design.md>), [Microservice](<https://devfeed.tech/topics/microservice.md>), [Microservices](<https://devfeed.tech/topics/microservices.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [autonomy](<https://devfeed.tech/tags/autonomy.md>), [build-times](<https://devfeed.tech/tags/build-times.md>), [gradle](<https://devfeed.tech/tags/gradle.md>), [independent](<https://devfeed.tech/tags/independent.md>), [microservices](<https://devfeed.tech/tags/microservices.md>), [software-development-team-topologies-engineering-excellence-organizational-design](<https://devfeed.tech/tags/software-development-team-topologies-engineering-excellence-organizational-design.md>)

### AI overview

The article argues that fast-growing companies should reduce unnecessary alignment requirements by structuring teams and systems for greater independence. It discusses cross-functional units, vertical ownership, microservices, distinct modules, and splitting frontend and backend dependencies.

### Source excerpt

Just care less about not being aligned If you work in a company that is aiming for fast growth, being overly aligned will slow you down as the number of stakeholders increases. If every time I want to introduce a new linting rule I would need to agree with 55 other developers, I will likely not do it. Instead of forcing all units to use the same tech stack, the same code style, the same testing framework and so on, we need to learn to just care less. Of course, the ability to care less depends on the architecture and the company structure. In a monolithic application, it is far more difficult to reduce the impact of units on each other, than in an environment of properly structured microservices. Thus, the goal is to identify and create structures that allow you to care less about alignment. The entire idea of cross-functional units is aiming for units to be independent. This is achieved by having units own vertical slices of the system completely, which reduces the need for alignment with other units to a minimum. However, sometimes even cross-functional units can influence each other because of technical dependencies or suboptimal structuring of these units.

## Cross-functional units and uni-functional teams

DevFeed: [Cross-functional units and uni-functional teams](<https://devfeed.tech/articles/cross-functional-units-and-uni-functional-teams-39886.md>)

Original publisher: [Read original article](<https://mende.io/blog/cross-functional-units-uni-functional-teams/>)

Author: tobi@techunicorn.builders (Tobias Mende)

Published: 2021-10-29T09:08:00Z

Content type: opinion

Language: en

Sources: [Tobias Mende](<https://devfeed.tech/sources/tobias-mende.md>)

Topics: [Architecture & Design](<https://devfeed.tech/topics/architecture-design.md>), [Back end](<https://devfeed.tech/topics/backend.md>), [Front end](<https://devfeed.tech/topics/frontend.md>), [cloud-infrastructure](<https://devfeed.tech/topics/cloud-infrastructure.md>), [DevOps](<https://devfeed.tech/topics/devops.md>)

Tags: [autonomy](<https://devfeed.tech/tags/autonomy.md>), [backend](<https://devfeed.tech/tags/backend.md>), [cloud-infrastructure](<https://devfeed.tech/tags/cloud-infrastructure.md>), [components](<https://devfeed.tech/tags/components.md>), [designer](<https://devfeed.tech/tags/designer.md>), [devops](<https://devfeed.tech/tags/devops.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [qa](<https://devfeed.tech/tags/qa.md>), [software-development-team-topologies-engineering-excellence-organizational-design](<https://devfeed.tech/tags/software-development-team-topologies-engineering-excellence-organizational-design.md>), [teams](<https://devfeed.tech/tags/teams.md>)

### AI overview

The article compares cross-functional units, where people from multiple disciplines work autonomously on an area end to end, with uni-functional teams that connect specialists across units. It argues that cross-unit coordination is especially valuable when teams share code, services, frontends, or infrastructure, helping align practices and address issues that affect multiple units.

### Source excerpt

Cross-functional units and uni-functional teams Many modern companies put a high emphasis on having multiple functions within one unit or team. The goal: The unit should be able to function with a high degree of autonomy, working on its area and owning everything in this area from beginning to end.