Phil on Nostr: There are a bunch of different ways to slice the team documentation problem: * What ...
There are a bunch of different ways to slice the team documentation problem:
* What do we do?
* How do we do it?
* What do we use to get things done?
* Where do we go?
Different written material serves different purposes:
* Knowledge acquisition and application (learning)
* Activity guidance (how-to, standards and processes)
* Reference material (configuration, tuning, maintenance and service management)
Published at
2024-07-22 22:05:44Event JSON
{
"id": "2841ad82fad05619b212ec56d106de96a089231511ad8a175c3302ff567d880e",
"pubkey": "97188eaa455613e1c3bc603ed6274158e6ca9ecf2ea0f6ab8677e8949ee3280c",
"created_at": 1721685944,
"kind": 1,
"tags": [
[
"e",
"d911719c8e4eac57852b763a472dd9336b554499709d4f0408816cafe95fd064",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://mstdn.io/users/paw/statuses/112832410043855539",
"activitypub"
]
],
"content": "There are a bunch of different ways to slice the team documentation problem: \n* What do we do?\n* How do we do it?\n* What do we use to get things done? \n* Where do we go?\n\nDifferent written material serves different purposes: \n* Knowledge acquisition and application (learning)\n* Activity guidance (how-to, standards and processes)\n* Reference material (configuration, tuning, maintenance and service management)",
"sig": "1fe21e37aa68406a3941b6d9f41d0e4ff91aac0d10622fdce26417cde820a30ef859ba237acb79b5cdbbe22812def1327ac80a6098bdc3868e51bc521913b29b"
}