Communication
Communication is the exchange of information, meaning, or signals between people, groups, agents, devices, or software components.
Lead Developer Career Guide
The exchange of information among team members and other stakeholders.
- How it is used
- Positions communication as the lead developer’s way to connect developers with project teams, clients, and stakeholders.
- How deep it goes
- Works through audience choice, feedback, disagreement, and follow-up as workplace practices rather than prescribing a single communication method.
- Examples
- Uses a Jira adoption disagreement and project-estimation feedback to show communication across authority and team boundaries.
- What you can do after
- Practice/perform clearer proposals, two-way feedback, and constructive disagreement while representing a development team.
Read how Lead Developer Career Guide explains communication →
Think Like a Software Engineering Manager
Communication is the exchange and interpretation of information, intentions, and feedback between people or groups.
- How it is used
- Uses communication to align engineering teams, manage performance, delegate work, and collaborate with cross-functional partners.
- How deep it goes
- Develops practical habits for tailoring messages, listening, confirming understanding, documenting agreements, and sustaining feedback loops rather than a formal communication model.
- Examples
- Illustrates alignment through a road-map meeting and follow-up email, and compromise through a disputed operational-readiness document.
- What you can do after
- Practice/perform clearer two-way conversations, confirm delegated tasks, record agreements, and invite feedback before misunderstandings grow.
Read how Think Like a Software Engineering Manager explains communication →
Grokking Concurrency
Communication is the exchange of information or coordination signals between concurrent tasks, processes, or threads.
- How it is used
- Organizes data exchange and coordination after a problem is divided into concurrent tasks.
- How deep it goes
- Explains communication choices and their costs through design examples, leaving some matrix storage decisions to later stages.
- Examples
- Uses a road-trip planning analogy, matrix calculations, and a cluster word count to illustrate communication needs.
- What you can do after
- Evaluate communication strategies by considering dependencies, waiting, data movement, and storage costs.
The Creative Programmer
Communication is the exchange of information, ideas, or intentions between people or groups.
- How it is used
- Uses communication to sustain creative collaboration, coordination, feedback, and knowledge sharing in software teams.
- How deep it goes
- Explains team-level communication through coordination failures, community smells, feedback, and an empathetic conflict-response practice.
- Examples
- Uses named community smells, a disputed technical claim, pair programming, and understandable code as concrete situations.
- What you can do after
- Apply it to identify communication obstacles, invite critical feedback, and address disagreement without escalating conflict.
Tech Startup Toolkit
Communications are organized activities for conveying messages and information to internal or external audiences, including a company's investors.
- How it is used
- Uses communication to establish a startup’s presence, maintain stakeholder trust, and keep investors supportive through routine and difficult periods.
- How deep it goes
- Explains communication’s purposes, monthly investor cadence, bad-news handling, and layoff messaging without supplying a detailed update template.
- Examples
- Uses monthly investor updates, pandemic uncertainty, hidden bad news, small investors, and layoff announcements as practical cases.
- What you can do after
- Operate regular, candid updates for investors and employees during fundraising, setbacks, pivots, and layoffs.
Interview Speak
The exchange of information between people or groups through shared messages or signals.
- How it is used
- Uses communication to explain benefits, influence decisions, coordinate groups, and demonstrate workplace effectiveness.
- How deep it goes
- Develops communication through examples and critiques, but stops short of formal communication theory or detailed process design.
- Examples
- Uses failed persuasion, cross-country customer coordination, quantified sales results, and critiques of vague answers.
- What you can do after
- Apply it by giving specific communication examples that show audience, actions, adaptation, and measurable results.
"Looks Good to Me"
The exchange of information and meaning between participants through shared messages and interpretation.
- How it is used
- Strengthens code reviews, emergency follow-up, and collaborative engineering practices through shared expectations, clarity, and trust.
- How deep it goes
- Explains communication through review responsibilities, constructive comments, automation, documentation, and postincident follow-up.
- Examples
- Uses code review comments, emergency procedure records, and pair programming alongside code reviews as concrete communication settings.
- What you can do after
- Apply it by writing constructive review comments, clarifying responsibilities, and communicating documented outcomes after emergencies.
Acing the Frontend Interview
Communication is the exchange of data and control signals among components of a distributed system.
- How it is used
- Frames communication as the reliability foundation for replica synchronization, shard reassignment, and distributed health checks.
- How deep it goes
- Moves from replication definitions to RPC, queues, retries, timeouts, backpressure, locality, batching, and compression.
- Examples
- Uses synchronous and asynchronous replication, RPC, queues, replication events, shard reassignments, health checks, and large migrations.
- What you can do after
- Evaluate replication and messaging choices by comparing consistency, latency, fault tolerance, and failure-handling mechanisms.
Read how Acing the Frontend Interview explains communication →
Software Architecture Decision-Making
Architectural communication is the deliberate exchange of architectural intent, decisions, trade-offs, and consequences among people involved in a system.
- How it is used
- Turns architectural intent into shared decisions that teams can understand, trust, and act on.
- How deep it goes
- Explains stakeholder translation, trust, and coordination, but does not prescribe detailed communication techniques.
- Examples
- Uses differing stakeholder views and retry logic as concrete illustrations of communication’s architectural role.
- What you can do after
- Apply communication to translate goals, limitations, risks, and trade-offs into shared architectural direction.
Read how Software Architecture Decision-Making explains communication →
Also covered in
- Think Like a CTO
- Inside AI
- Collaborative Software Design: How to facilitate domain modeling decisions
- The Art of Code
- AI Agents in Action
- Everyday Data Visualization
- 100 Go Mistakes and How to Avoid Them
- The Coder CafeIn early access (MEAP)
- Timeless Algorithms, The Foundational IdeasIn early access (MEAP)
- Build a DeepSeek Model (From Scratch)In early access (MEAP)
- AI for Everyday IT
- Cyber Threat Hunting
What to know first
- stakeholderA stakeholder is a person, group, or organization with an interest in, influence over, or potential to be affected by a system, project, decision, or its outcomes.
- collaborationCollaboration is the coordinated work of multiple participants who contribute toward a shared goal or outcome.
- clientA client is a person, organization, device, or software component that receives or uses a product, service, resource, or functionality provided by another party or system.
- feedbackFeedback is information or evaluation about an action, system, or outcome that can inform assessment or subsequent decisions and behavior.
Related concepts
- emotional intelligencepart of · Emotional intelligence is the capacity to recognize, understand, regulate, and respond appropriately to emotions in oneself and others.
- asynchronous communicationincludes · Asynchronous communication is the exchange of information without requiring participants to interact at the same time or the sender to wait for the receiver to process a message.
Questions about communication
What is communication?
Communication is the exchange of information, meaning, or signals between people, groups, agents, devices, or software components.
Which Manning books explain communication?
Lead Developer Career Guide, Think Like a Software Engineering Manager, Grokking Concurrency, The Creative Programmer, Tech Startup Toolkit, Interview Speak, "Looks Good to Me", Acing the Frontend Interview and 1 more.
What should I know before learning communication?
Manning books that teach communication usually introduce stakeholder, collaboration, client and feedback first.
What kinds of communication are there?
Kinds of communication include asynchronous communication, face-to-face communication, inter-node communication, machine-to-machine communication and two-way communication.
What is communication part of?
Communication is part of emotional intelligence. Emotional intelligence is the capacity to recognize, understand, regulate, and respond appropriately to emotions in oneself and others.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.








