Communication for engineers
33 moments from 28 videos · 1:52:41 total
Technical skills are only half the battle. These curated talk segments help engineers refine their written and verbal communication styles for better collaboration across departments.
Centralizing team communication to avoid information silos
Conducting discussions within trackable tickets rather than private messages keeps the entire engineering team informed.
Three examples of failed communication in engineering teams
Critical technical information often vanishes during standard agile ceremonies despite the presence of competent teams and established workflows.
Effective strategies for employees to increase their workplace visibility
How engineers can communicate career goals and take on impactful responsibilities to advance.
Maintaining technical authenticity and connection in engineering leadership roles
Staying connected with developer teams helps managers retain their engineering identity while leading.
Setting foundational rules for exploring unconventional engineering communication
Three practical requests for actively experimenting with and adapting disruptive conversational techniques.
Moving past communication demands to structural engineering changes
Addressing a monolithic notification bug highlights why introducing automated dependencies is better than telling teams to communicate more.
Communicating progress asynchronously across distributed engineering teams
Sharing weekly performance charts with preemptive technical context builds cross-team consensus and reduces friction for resolving blockages.
Understanding engineering career opportunities within enterprise consulting structures
A breakdown of necessary communication rhythms and standard software architecture obligations inside professional services.
Fostering engineering culture through internal events and communications
The organization cultivates a cohesive developer community by leveraging internal tech conferences, cross-location meetups, and curated newsletters.
Building collaborative partnerships across cross functional product teams
Continuous communication between engineering and design produces highly refined product functionality.
Democratizing feature prototyping for non-technical product managers
How product managers can leverage AI tools to create functional prototypes and improve engineering communication.
Applying psychology to software development and engineering workflows
Utilizing psychological concepts to improve communication between engineering and management regarding technical debt.
Future predictions for engineering skills and software development tools
Essential skills for long-term engineering success hinge heavily on clear communication and critical problem solving.
Establishing developer advocacy and technical evangelist roles
Bridging the communication gap between engineers and non-technical staff requires dedicated individuals who understand both code and corporate strategy.
Reflecting on engineering motivations and undervalued strengths
Critical non-technical skills like empathy and communication often drive success but remain frequently overlooked in technical environments.
Bringing the engineers to the problem domain
Forming small, targeted groups around specific issues aligns communication structures with the desired software outcomes.
Prioritizing engineering culture over immediate architectural changes
Conway's law indicates that engineering culture and communication patterns will override forced changes to system architecture.
Maintaining appropriate vocabulary by avoiding informal slang
Treating the discussion collegially does not excuse the use of profanity or excessively casual jargon with senior engineering staff.
Prioritizing communication and structural awareness over strict tool mastery
Exceptional interpersonal abilities and a holistic understanding of the software lifecycle strongly differentiate leading platform engineers.
Building engineering communities and finding technical inspiration
Engaging with colleagues and developer communities provides valuable insights into complex engineering roles like site reliability and operations.
Establishing mutual trust through cross functional design and data
Utilizing objective metrics and actively involving engineers in program creation firmly establishes the psychological safety needed for candid communication.
Bridging high context and low context workplace communication styles
Translating abstract company values into clear behavioral expectations reduces frustration among software engineers who rely heavily on direct clarity.
Multiplying technical impact by teaching and sharing engineering knowledge
Shifting from a strict coding mindset to documenting solutions scales engineering output across external communities.
Aligning cross-team goals and prioritizing backlog improvements
Fostering communication across engineering departments to prioritize reliability issues ahead of scheduled system upgrades.
Mastering project languages for efficient communication and collaboration
Using unified terminology across domain, technical, and architectural categories reduces chaotic communication and prevents implementation misunderstandings.
Recognizing technical components and proper engineering process alignment
Creating an architecture that accommodates change involves organizing high-level capabilities alongside specific communication patterns defined by conways law.
Managing cultural differences in direct engineering feedback
Carving out dedicated time for collaborative pre-meetings mitigates misunderstandings caused by blunt communication styles.
The impact of artificial intelligence on talent sourcing
Why the integration of artificial intelligence into recruitment workflows necessitates a deeper understanding of technical communication and prompt engineering.
Overcoming miscommunication and differing technical interpretations across teams
Because technical vocabulary carries subjective meanings across departments, clarifying ambiguous terms prevents dangerous misalignments during cross-functional collaboration.
Leveraging nonverbal communication to reinforce technical leadership authority
Because poor delivery diminishes perceived competence, utilizing strong nonverbal cues and presentation formats prevents engineers from unintentionally undermining their authority.
Mapping business criticality to surface organizational gaps
Assessing revenue and compliance obligations reveals hidden architectural bottlenecks and communication overhead in engineering teams.
Sourcing reliable technical intelligence from experienced peers and networks
How direct conversations at engineering conferences provide far better insights than generic blog posts or marketing materials.
Navigating text-heavy team communication as a developer
Replacing hard-to-read text messages with verbal conversations prevents miscommunication in software teams.
Your mix. Instantly.
More mixes
AI & Machine Learning
AI coding agents
AI & Machine Learning
MCP (Model Context Protocol)
AI & Machine Learning
RAG
Languages & Frameworks
TypeScript
Languages & Frameworks
React
Languages & Frameworks
Java
Cloud, Platform & Data
Platform engineering
Cloud, Platform & Data
Observability
Cloud, Platform & Data
Infrastructure as code
Architecture, Quality & Security
System architecture
Architecture, Quality & Security
Code review
Architecture, Quality & Security
Software supply chain security
Leadership, Career & Community
Engineering strategy
Leadership, Career & Community
Developer experience
Leadership, Career & Community