"How to communicate" textbook : Tori Iyuki / Yuko Kubo

Product description ※Please note that product information is not in full comprehensive meaning because of the machine translation.

Information Science
Technology alone is not enough to prevent code reviews from falling apart. Learn techniques for smooth text communication. Code reviews are an important process of improving the quality of products your team develops. However, in code reviews based on online text communication, there are frequent mistakes such as "the intention is not conveyed correctly" or "the receiver takes it negatively", which often lead to rework and misunderstanding. This book explains techniques for "Transmitted Code Reviews" that prevent such intentions and feelings from being transmitted. Based on 19 specific case scenes, this book explains in detail how to write easy-to-understand pull requests and review comments and how to proceed with effective reviews. The case scenes include cases of miscommunication that are common in code reviews at the development site, such as when tense review comments are returned, when PR without sufficient explanation is submitted, and when there are differences in ideas and values. With cute Mr. Character, this book contains guidelines for better code reviews for development teams that have problems and countermeasures, and proposes practical solutions approaches. For development teams that have problems such as "the intention of reviewing becomes a dispute over pointing out" and "comments that don't understand what you want to convey" are scattered around, this book should provide guidelines for better code reviews. For development teams that have problems such as "the intention of reviewing becomes a dispute over pointing out" and "comments that don't understand what you want to convey", this book should provide guidelines for solving problems. For development teams that have problems such as "the intention of reviewing becomes a dispute over pointing out" and "comments that don't understand what you want to convey", this book should provide guidelines for better code reviews. For development teams that have problems such as "the intention of reviewing becomes a dispute over pointing out" and "comments that don't understand what you want to convey", this book should provide guidelines for better code reviews. For development teams that have problems such as "the intention of reviewing becomes a dispute over pointing out" and "comments that don't understand what you want to convey", this book should provide guidelines for better code reviews. For those who have problems such as "just in case", confirm what you don't understand, add your own thoughts and opinions, clarify details, confirm "just in case", push ahead well, narrow down what you want to hear, post before / after images, prepare templates, label., and many other practical TIPS! Target audience : Field engineers who want to know how to do code reviews better, field engineers who want to know how