From 887cd28206ed095f0e8ba4faf4a7a2d675cefb59 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=2E=20Fernando=20S=C3=A1nchez?= Date: Thu, 6 Mar 2025 07:55:20 +0100 Subject: [PATCH] add mention to Oxide --- .gitignore | 1 + content/post/efficient-collaboration.md | 4 ++++ 2 files changed, 5 insertions(+) diff --git a/.gitignore b/.gitignore index 140c8b6..ce5d2dd 100644 --- a/.gitignore +++ b/.gitignore @@ -6,3 +6,4 @@ output *.pid *.pyc _gen +*/_gen diff --git a/content/post/efficient-collaboration.md b/content/post/efficient-collaboration.md index 05519a5..c6d90f7 100644 --- a/content/post/efficient-collaboration.md +++ b/content/post/efficient-collaboration.md @@ -257,6 +257,10 @@ Whenever a member asks you something useful that is not documented, don't just a Take the time to add this information yourself (e.g., by copy-pasting your response) or task that member with expanding the documentation themselves once they find an answer. If your organization's culture does not encourage using these docs, they will quickly get outdated and fall out of use. +One example of taking this documentation approach really seriously is [Oxide (computer company)](https://oxide.computer/). +They have a process they call [Request For Discussion (RFD)](https://rfd.shared.oxide.computer/), which they use to discuss and document both technical and organizational decisions. +For instance, they have [RFDs on why they record every meeting](https://rfd.shared.oxide.computer/rfd/0537), [RFDs about their choice of database](https://rfd.shared.oxide.computer/rfd/0110), and even [an meta-RFD that discusses the motivation RFDs and how the process should work](https://rfd.shared.oxide.computer/rfd/0001). + #### Trust your teammate's ability to learn