# Communication Breakdown - Kevin Galligan

DevFeed: [Communication Breakdown - Kevin Galligan](<https://devfeed.tech/articles/communication-breakdown-kevin-galligan-38176.md>)

Original publisher: [Read original article](<https://touchlab.co/communication-breakdown>)

Published: 2017-10-02T16:00:13Z

Content type: opinion

Language: en

Sources: [Touchlab | Enterprise Mobile Innovation & Development](<https://devfeed.tech/sources/touchlab-enterprise-mobile-innovation-development.md>)

Topics: [Development](<https://devfeed.tech/topics/development.md>), [Code](<https://devfeed.tech/topics/code.md>), [Mobile](<https://devfeed.tech/topics/mobile.md>)

Tags: [business](<https://devfeed.tech/tags/business.md>), [code](<https://devfeed.tech/tags/code.md>), [code-sharing](<https://devfeed.tech/tags/code-sharing.md>), [development](<https://devfeed.tech/tags/development.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [thoughts](<https://devfeed.tech/tags/thoughts.md>)

## AI overview

This commentary argues that specialized teams and shared code can work well when downstream developers can debug, edit, and contribute to the shared code. Siloed code creates bottlenecks, increases the burden on upstream teams to be correct, and can leave downstream teams waiting when problems arise.

## Source excerpt

In my experience, having specialized teams and parts of code is good, but having siloed teams and code is bad, or at least more difficult.