# Practices, Software-Development, Organizational-Design, Software-Craft

Published articles for Practices, Software-Development, Organizational-Design, Software-Craft.

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

## Code ownership conflicts as a signal for structural mismatch

DevFeed: [Code ownership conflicts as a signal for structural mismatch](<https://devfeed.tech/articles/code-ownership-conflicts-as-a-signal-for-structural-mismatch-39879.md>)

Original publisher: [Read original article](<https://mende.io/blog/code-ownership-conflicts/>)

Author: tobi@techunicorn.builders (Tobias Mende)

Published: 2022-02-19T12:54: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>), [software-architecture](<https://devfeed.tech/topics/software-architecture.md>), [Code](<https://devfeed.tech/topics/code.md>), [Software](<https://devfeed.tech/topics/software.md>)

Tags: [architecture](<https://devfeed.tech/tags/architecture.md>), [code](<https://devfeed.tech/tags/code.md>), [components](<https://devfeed.tech/tags/components.md>), [conway-s-law](<https://devfeed.tech/tags/conway-s-law.md>), [practices-software-development-organizational-design-software-craft](<https://devfeed.tech/tags/practices-software-development-organizational-design-software-craft.md>), [software-architecture](<https://devfeed.tech/tags/software-architecture.md>), [teams](<https://devfeed.tech/tags/teams.md>), [transparency](<https://devfeed.tech/tags/transparency.md>)

### AI overview

This opinion article argues that team-level code ownership can reveal structural mismatches between team organization and software architecture. It explains how unclear ownership, especially in larger systems, can obscure subsystem boundaries and hidden knowledge gaps. Drawing on Conway's law and the Inverse Conway Manoeuvre, it presents aligned team and architectural boundaries as a way to reinforce system structure and surface ownership issues.

### Source excerpt

Code ownership conflicts as a signal for structural mismatch In my last article, I explained why I believe that individual code ownership is bad and why weak code ownership on a cross-team level can be highly beneficial.