Knowledge-Sharing with Design Docs

Shift’s engineering team has always had an informal process around design docs for new systems, but the process has varied from team to team and engineer to engineer. We’ve had the assumption that if a project or feature is expected to take more than a week or involve more than one engineer, it probably makes sense to document your design in advance so you can get feedback.

A few engineers from our infrastructure team recently formalized the process to add some consistency with the main goal of streamlining the process–we want the term “design doc” to mean the same thing to everyone and to prevent engineers from feeling like they have to reinvent the wheel every time. We also think design docs can be used for mentorship because they allow junior engineers to get feedback faster than through code reviews.

Continue reading “Knowledge-Sharing with Design Docs”