Sem título

Communication

everyone on a team has the same understanding of what is being built and why

conceptual integrity- both in how it is designed, but also how it is implemented

idea that whatever vision of what is being built must stay intact, even as the building of it gets distributed to multiple people

requires empathy and teamwork

if poor communications - teams become disconnected and produce software defects

powerful role in software projects that it even shapes how projects unfold

Conway’s Law- This theory argues that any designed system—software included—will reflect the communication structures involved in producing it

if those two teams meet regularly to design the error mesages together, communicating their shared knowledge, they might produce a seamless, coherent experience

seeking information to further their work, going to their coworkers’ desks, emailing them, chatting via messaging platforms, and even using social media

highly problematic in software engineering teams. For example, Perlow

highly dysfunctional use of interruptions in which the most expert members of a team were constantly interrupted to “fight fires”

also about relationships and identity

work environments are still dominated by men, who speak loudly, out of turn, and disrespectfully, with sometimes sexual harassment

cultural competence (the ability for individuals and organizations to work effectively when their employee’s thoughts, communications, actions, customs, beliefs, values, religions, and social groups vary)

software developers have to work with people in other domains such as artists, content developers, data scientists, design researchers, designers, electrical engineers, mechanical engineers, product planners, program managers, and service engineers

required open-mindedness about the input of others, proactively informing everyone about code-related constraints, and ultimately seeing the broader picture of how pieces from different disciplines fit together

reducing the amount of communication necessary is knowledge sharing tools

any information system that stores facts that developers would normally have to retrieve from a person

By storing them in a database and making them easy to search, teams can avoid interruptions

eg. GitHub pages or Slack teams, stack overflow

stack overflow - archives facts about programming language and API usage

newcomers join a team and lack the right knowledge, they introduce defects

try to mitigate this by rotating developers between projects, “cross-training” them to ensure that the necessary knowledge to maintain a project is distributed across multiple engineers

don’t underestimate the importance of talking. Know who you need to talk to, talk to them frequently, and to the extent that you can, write down what you know both to lessen the demand for talking and mitigate the risk of you not being available, but also to make your knowledge more precise and accessible in the future