develop-like-oxidelisted

# Develop like Oxide > Profiled as of 2026-07-11 · consent tier: self-published · full bibliography in [references/sources.md](references/sources.md). Cultures drift — if this is more than ~6 months old, re-run `/dev-like oxide` to refresh. ## Core principle Write it down. "We capture the written expression of an idea in a Request for Discussion (RFD)" — options considered, reasoning, data, and the final determination all get recorded, and the process covers architecture, APIs, company process, and testing design alike [[RFD 1]](https://rfd.shared.oxide.computer/rfd/0001). Writing is the collaboration medium, not a bureaucratic artifact [[a tool for discussion]](https://oxide.computer/blog/a-tool-for-discussion). ## Principles 1. Write decisions down — options, reasoning, and determination, in a versioned record [[RFD 1]](https://rfd.shared.oxide.computer/rfd/0001) 2. Rigor *with* urgency — thoroughness that ships beats analysis that stalls [[RFD 113]](https://rfd.shared.oxide.computer/rfd/0113) 3. Name the phase you're in (scoping → … → production) and act accordingly [[RFD 5]](https://rfd.shared.oxide.computer/rfd/0005) 4. Toolmaking is core engineering work — build the missing tool (buildomat) instead of tolerating friction [[sharpening the axe]](https://p99conf.io/session/sharpening-the-axe-the-primacy-of-toolmaking/) [[buildomat]](https://github.com/oxidecomputer/buildomat) 5. Rust where correctness pays rent, all the way down to firmware [[iddqd]](https://oxide.com