Sketchbooks
This is interesting because Murphy recently started calling these, "Sketchbooks", I like the way he put it:
This is a place for documents that exist as chronologically structured, largely unedited stream of consciousness from the brain of a developer while working on a particular issue. I call them sketchbooks, because they make me think of the notebook and pen an artist carries with them out into the world when they go out to observe and learn about the world. They produce sketches that help them learn about the shape, form, and color of the things they see. Sometimes the sketches are great, but mostly they are messy & full of mistakes. They are the means to the end of greater learning. Think of these documents as messy sketches produced while learning. We keep them around so that they can be referenced later if another developer happens to come upon the same problem again and needs inspiration from past work.
Reminds me of Drawing isn't like a printer, even though it's not the same idea, it's just interesting how much drawing is a good analogy for things.
Overall I think this is interesting but also feel like if you talk in context, namely under a Todo in Basecamp and Under a PR or Issue in Github. Saving these away in an unstructured list is better than Slack because it's not topic fragmentation and it's not rushed. But at the same time feels like it would be very hard to find in the future. Namely, I think it lacks Information Discoverability.
Backlinks: