[1/2] Communication Patterns: A Guide for Developers and Architects (Communication Patterns: A Guide for IT Developers and Architects) (Category Management)
I started reading it in English as an early preview on the O’Reilly platform, and finished it as a book in Russian, which was translated and published by BHV. In general, I liked the book - it is about successful communication for engineers and technical managers who are already accustomed to using templates in design, development and organizational design. Author: Jackie Reed (Jacqui Read) - decision architect (Solution & Enterprise Architect) British. She started out as a full-stack developer and later moved into architecture and promoted the idea that communication is a skill like writing code and can be systematized. Instead of “be clearer” advice, she suggests specific patterns. (provenance) and antipatterns (typical).
When it comes to the book, it is divided into 4 part 13 Chapters that consistently close all communication channels: from visual circuits to asynchronous work.
1альная Visual communication (Visuals) It’s about how to create diagrams that really read and understand. - Head. 1. Basics of communication (Communication Essentials). This is the foundation of the book: Know Your Audience and Managing Levels of Abstraction. It explains why it is impossible to mix business context and implementation details on the same scheme. - Head. 2. Noise reduction (Clarify the Clutter). Here the author tells you how to clear the diagrams of unnecessary elements that distract attention. It is about combating visual debris to increase readability. - Head. 3. Accessibility (Accessibility). This is an important topic that is often overlooked: how to make circuits understandable for people with colorblindness or perceptual disabilities. (For example, do not rely on color alone.). This is sometimes overlooked in consumer products.
- Head. 4. Narrative (Narrative). The diagram should tell a story. The Big Picture First pattern (The Big Picture Comes First) It teaches the viewer to immerse himself in context before drowning him in detail. By the way, I have one. selection storytelling and history books - Head. 5. Notation. (Notation). The chapter is about how to choose the level of formality of notation depending on the task, and why a legend to the scheme is mandatory. - Head. 6. Composition (Composition). Principles of visual hierarchy: how to arrange elements so that the viewer’s gaze slides along the scheme in the correct order, reading the logic of the system.
2Written and oral communication (Written, Verbal, and Non-verbal) Moving from pictures to words and speeches. - Head. 7. Written communication (Written Communication). Patterns for documentation and correspondence. How to Write Concisely, Structure Technical Texts and Avoid Text Walls It's also about the Minto pyramid I'm talking about. told earlier. - Head. 8. Verbal and nonverbal communication (Verbal and Nonverbal Communication). A chapter on how our gestures, tone and posture affect the perception of technical decisions. How to read the audience reaction during a presentation - Head. 9. Rhetorical Triangle (The Rhetoric Triangle). Adaptation of the Ancient Aristotle Principle (Ethos, Pathos, Logos.) for engineers. How to Balance Between Logic (factual)authority and emotions for persuading stakeholders. Details in post
I will tell you about the rest of the book in the continuation of this post.
#Thinking #Writing #Leadership #Management #DistributedSystems #Architecture #SoftwareArchitecture #SystemDesign #Software #Writing #Speaking