Vendor Profile
Shoeisha Co., Ltd.
| Address | 5 Funamachi Shinjuku-ku Tokyo, JAPAN ZIP:160-0006 |
|---|---|
| Representative Name | Kaoru Usui |
| Annual Revenue | closed |
| No. of Employees | 185 |
| Web Site URL |
SD item code:13438787
| Detail | Price & Quantity | ||
|---|---|---|---|
| S1 |
Yuki Torii, Yuko Kubo, Ayaka Moronaga (Author)
Supervised by Koji Shimada
 Original text before translation
鳥井 雪、久保 優子、諸永 彩夏 (著)
島田 浩二 監修
(186000)
JAN:9784798186009
|
(186000)
JAN:9784798186009
Wholesale Price: Members Only
1 pc /set
In Stock
|
|
| Shipping Date |
|---|
|
About 1 week
|
| Dimensions |
|---|
|
Format:A5
Number of pages:224 |
| Specifications |
|---|
|
Country of manufacture: Japan
Material / component: Format:Book (paper)
Year of manufacture: 2025
Product tag: None
|
Description
| You want to facilitate code reviews. Learn efficient text communication techniques. Code review is an important process to improve the quality of products developed by a team. However, in code reviews, which are based on online text communication, misunderstandings such as "the intent is not conveyed correctly" and "the recipient may take it negatively" occur frequently, often resulting in rework and misunderstandings. This book explains the techniques of "communicative code review" that prevents such misunderstandings of intentions and feelings. Based on 19 specific case studies, the book explains in detail how to write easy-to-understand pull-request* review comments and how to proceed with effective reviews. The case study scenes are, *When tense review comments are returned *When a PR is submitted with insufficient explanation *When ideas and values differ and other cases of miscommunication that are common in code reviews at development sites. Together with cute characters, the book organizes the causes and countermeasures of problems and proposes practical approaches to solving them. [It's supposed to be a review, but it turns into a pointing out battle.] [Comments that don't convey what they are trying to convey are flying all over the place.] For development teams that have such problems, this book should serve as a guideline for better code reviews. This book will help you learn the techniques for smooth code review, so that review points can be conveyed accurately and reviewers can improve their work with a sense of satisfaction. *Explanatory TIPS (in part) Don't give quizzes / Think in good faith / Create tags to be shared by the team / Keep a work log and link to references / Set a time limit for consultation / Tell what level you don't understand / Add your own ideas * opinions / Provide clear details / Confirm [just in case] / Prompt skillfully / Focus on what you want to ask / Include a before/after picture/provide a template/label ...... And many other practical tips! |
More
| Shipping Method | Estimated Arrival |
|---|---|
| Sea Mail | From Jun.4th 2026 to Aug.6th 2026 |
| Air Mail | From May.19th 2026 to May.21st 2026 |
| EMS | From May.18th 2026 to May.21st 2026 |
| Pantos Express | From May.20th 2026 to May.25th 2026 |
| DHL | From May.18th 2026 to May.20th 2026 |
| UPS | From May.18th 2026 to May.20th 2026 |
| FedEx | From May.18th 2026 to May.20th 2026 |
|
Some trading conditions may be applicable only in Japan.
This product (book) is subject to the Resale Price Maintenance Program. The law allows the manufacturer (publisher) to specify the sales price. We ask that your company also adhere to the resale price specified by us. In the unlikely event that you fail to do so, we may terminate the transaction. Thank you very much for your understanding and cooperation.
|
Other items from this category:
Learn efficient text communication techniques.
Code review is an important process to improve the quality of products developed by a team. However, in code reviews, which are based on online text communication, misunderstandings such as "the intent is not conveyed correctly" and "the recipient may take it negatively" occur frequently, often resulting in rework and misunderstandings.
This book explains the techniques of "communicative code review" that prevents such misunderstandings of intentions and feelings. Based on 19 specific case studies, the book explains in detail how to write easy-to-understand pull-request* review comments and how to proceed with effective reviews.
The case study scenes are,
*When tense review comments are returned
*When a PR is submitted with insufficient explanation
*When ideas and values differ
and other cases of miscommunication that are common in code reviews at development sites. Together with cute characters, the book organizes the causes and countermeasures of problems and proposes practical approaches to solving them.
[It's supposed to be a review, but it turns into a pointing out battle.]
[Comments that don't convey what they are trying to convey are flying all over the place.]
For development teams that have such problems, this book should serve as a guideline for better code reviews. This book will help you learn the techniques for smooth code review, so that review points can be conveyed accurately and reviewers can improve their work with a sense of satisfaction.
*Explanatory TIPS (in part)
Don't give quizzes / Think in good faith / Create tags to be shared by the team / Keep a work log and link to references / Set a time limit for consultation / Tell what level you don't understand / Add your own ideas * opinions / Provide clear details / Confirm [just in case] / Prompt skillfully / Focus on what you want to ask / Include a before/after picture/provide a template/label ...... And many other practical tips!