- #108
- #107
- #106
- #105
- #104
- #103
- #102
- #101
- #100
- #99
- #98
- #97
- #96
- #95
- #94
- #93
- #92
- #91
- #90
- #89
- #88
- #87
- #86
- #85
- #84
- #83
- #82
- #81
- #80
- #79
- #78
- #77
- #76
- #75
- #74
- #73
- #72
- #71
- #70
- #69
- #68
- #67
- #66
- #65
- #64
- #63
- #62
- #61
- #60
- #59
- #58
- #57
- #56
- #55
- #54
- #53
- #52
- #51
- #50
- #49
- #48
- #47
- #46
- #45
- #44
- #43
- #42
- #41
- #40
- #39
- #38
- #37
- #36
- #35
- #34
- #33
- #32
- #31
- #30
- #29
- #28
- #27
- #26
- #25
- #24
- #23
- #22
- #21
- #20
- #19
How do different teams consolidate and document development practices?
- Handover between team departments
- Architectural design choices, technical background
- Team synergy
- …
I really want to improve team documentation, but I always find it hard to find time to record experiences and consensus. Even when documents are recorded, there is no time to digest them, and they often get forgotten in some corner.
The recent goal is: in the product, I hope to start trying to implement a BDD (Behavior-driven development) model that integrates testing, development, and business in new projects, allowing different fields to jointly maintain and collaborate on unified documentation. As for the fragmented knowledge and pitfall experiences, they are currently managed and recorded in Notion, and I need to find time to organize and archive them to ensure that new joiners can get up to speed immediately!
Seeing the technical blogs of impressive companies is quite inspiring: dropbox.tech
- #18
- #17
- #16
- #15
- #14
- #13
- #12
- #11
- #10
- #9
- #8
- #7
- #6
- #5
- #4
- #3
- #2
- #1