This session teaches the basics of the design docs (also known as technical specifications) needed for product development. It also explains how to write a good design doc and how design docs are used at Mercari.
for developers and other stakeholders, guiding them through the design and implementation process - Communicate Decisions - Documents the logic behind architectural design choices, ensuring clarity and understanding among team members
system’s architecture & design • Roadmap for Development ◦ Implementation roadmap, components interaction, technical details ◦ Speed up development • Risk Mitigation ◦ Identify potential risks and challenges early • Documentation ◦ Reference doc throughout the development ◦ Aiding in maintenance and future enhancements • Deliver with Quality ◦ Getting feedback from various stakeholders ◦ Improve code review quality
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
ysknsid25
lycorptech_jp
cote
kazeburo
kimuson
cohalz
ryohysk
.png){kind=icon}
pharma_x_tech
altech
masakiokuda
yusukeshimizu
takufujii
philnash
holman
bluesmoon
hannesfritz
jonrohan
tammielis
tanoku
cassininazir
maggiecrowley
denniskardys
tammyeverts
thoeni
