alt Hacker NewsThis would have been very useful at my previous job. We had a gdrive folder with '2024' or '2025' with a bunch of google docs with no inter-linking between them. If you were lucky the title would be vaguely related to the topic you are working on, and maaaaaybe there'd be a link to prior work. Frequently I'd look at an RFC, see no approvals but then find out it _had_ been approved but nobody actually updated the document. Infurating.
I'm not sure the reason for friction. These are developers, they know how to use git etc, but management prefers google docs I suppose (previous iterations were confluence, then markdown on github).
I'm glad to hear you would have found it beneficial!
I've definitely seen the same patterns at companies (and even introduced similar patterns).
The proposal linking was inspired both by IETF RFCs and by Jira issues. I love how both systems provide semantic meanings to such links (X obsoletes Y).
I do hope to marry the engineering love of markdown with management's love of WYSIWYG. Currently the proposal editing process is done via a syntax-highlighted markdown editor but in the future I'll add a WYSIWYG editor, then let users select a default mode.