Problem solvers have trouble recalling what they know until they see a problem. We describe what to write when you realize you can barely count all the ways some bozo is wrong about some problem you've solved before.
Explain how you solved more than one problem even though you only remember one.
Explain how a web of forces conspire to link problems together in a way that can be teased apart, with effort.
Explain how the things you made, not the way you made them, offers the key to lasting knowledge.
Aside: Describe how the CHECKS pattern language emerged out of a stupid argument on the internet.
Explain what others need to know about your solutions, and what they don't.
Explain how to name your solutions with names that will stick outside of the space you found them.