3 ms·
An interesting way to approach the documentation issue discussed in this article is 'wiki bankruptcy': when a wiki goes stale, simply tell all devs to save what
by nexthash 6y ago
An interesting way to approach the documentation issue discussed in this article is 'wiki bankruptcy': when a wiki goes stale, simply tell all devs to save what they think is important before deleting the whole thing outright. Then, they can recreate those pages into a new wiki. Read more about it here:
https://critter.blog/2020/08/10/wiki-bankruptcy/ https://critter.blog/2020/08/10/wiki-bankruptcy/
He also talks about using this 'bankruptcy' philosophy in other aspects of life, which I thought was intriguing:
https://critter.blog/2020/09/24/declare-bankruptcy-and-dont-be-ashamed-of-it/ https://critter.blog/2020/09/24/declare-bankruptcy-and-dont-...
- wdfx 6y agoI think this approach should not be feared. Over the years I have 'bankrupted' several supporting systems, some more than once. I've deleted shit like - old tickets - documentation / wikis - old infrastructure - old backlogs I'm actually going through this process now with my current team. There's so much stuff we have written by our predecessors that is just no longer relevant. So, I've set up or renamed our Jira/confluence spaces and then move/copy back in only that content which is still relevant to us. Everything else will be archived. In this way, everything which comes out the end of this process: - is ours - has recently been seen/reviewed by at least one pair of eyes - is still relevant to the business and the product