Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

How do you reconcile your points 4 and 1? Say I want to answer someone's question on Slack. First I have to change the docs, but doing so would require a whole PR, alongside approval, which may take one or multiple days.


You can flip the order of the steps and it works pretty well imo: answer on Slack, and then once the discussion is complete, clean up the messages and put them into the docs.

This has the added benefit that you can have some back and forth to get to the root of the question before documenting it.

The key thing is that you have to make sure to actually do the step after (transfer to docs), even if it's a quick copy-paste with minimal editing.


You can point people at the answer in the PR, or you can relax approval requirements for docs changes, or you can be someone who actually can approve docs changes yourself. There can still be ownership in that model it just doesn't require pre-approval, only post-approval.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: