Artists and programmers often work together on complex projects in stressful environments and things don't always go smoothly. Miscommunication and misunderstandings are common as these two disciplines often use the same words to mean different things when they talk to each other. Unintentional slights can turn into long-held grudges and productivity grinds to a crawl.

This is a "flip book" that contains two narratives in one. Turn the book one way and read one perspective; turn the book over and upside down and read the other perspective. The narratives can be read separately, one after the other, or in alternating chapters. Talking to Artists / Talking to Programmers can help anyone who wants to improve communication with artists and programmers. It's set up like a foreign language dictionary, so it addresses the cultural norms, attitudes and customs surrounding the words each group uses, so you'll know not just what the words in the glossary mean, you'll know why they're used that way and how to get communication flowing again.

It addresses common reasons for communication problems between these two groups and provides specific suggestions for solutions. The unusual format allows for each side to be given equal weight - learn how to talk to artists starting on one side of the book, turn it over and learn how to talk to programmers. The whole book stresses the things artists and programmers have in common.

Focused primarily on videogame developers, it also applies to other fields where tech and art have to work together, including web developers and teams building mobile apps. Anyone who wants to communicate better with programmers or artists - this book can help

?

Features

• Lists of common problems and strategies for solving them
• Specific ideas for building bridges between departments
• Case studies from real teams
• Glossary of terms causing the most confusion
• Explanations for common friction points
• Approaches for fostering goodwill
• Solutions for team dynamics problems
• Specific suggestions for providing feedback
• Ideas for holding successful meetings

?