In this course, we will explain the basic concepts of using Design Doc for product development and introduce the template that is currently in use at Mercari. We will also cover how to write a good design doc and deal with it in Mercari.
or a system which includes the rationale for each decision made. The purpose of design doc is to aid in the critical analysis of a problem and the proposed solution while also communicating priority, effort and impact with different stakeholders
to that project • Speed up implementation by having a clear reference and direction • Improve quality by getting feedback from various stakeholders • Find flaws/issues before they happen • Improve code review quality • Get alignment with architecture and other technical detail • Help to onboard new members
code,and/or while prototyping By people having an insight for the domain Incorporate insight and idea Similar to “develop/review code” but It costs much less if written before actual code
Shared initial draft with teammates ◦ Update until find a stable version • Review ◦ Shared with wider audience • Implementation and Iteration ◦ Start implementation when reviews are done or almost done ◦ Update if anything minor changes while implementation ◦ For major changes create another version • Maintenance and Learning
different process ◦ Design Docs may be required before implementation of some features ◦ Other engineers or the tech lead may need to approve ◦ Templates might be different ◦ Some teams may not have a design doc flow • Individual ◦ Even if your team does not require it, you might write design docs for your own learning
mercari
masahirokawahara
tsukasa_ishimaru
miholovesq
cyberagentdevelopers
koujikozaki
lycorptech_jp
ryosk7
asa1984
tsukuha
scottboms
reverentgeek
phodgson
jlugia
marcduiker
quramy
carmenintech
sachag
smashingmag
vanstee
jeffersonlam
caitiem20
