Bookmarked Establishing a Culture of Thinking (It's About Learning)

Some simple ways to begin practicing documentation include:

  • Sharing a short video clip of documentation at the start of class or a meeting by displaying a brief clip and then asking students their thoughts about it.
  • Taking a photo of an especially powerful learning moment to revisit with students by using the classroom walls to display the documentation.
  • Jotting down a provocative or insightful quote from a student to share with the class via speech bubbles on the walls.
  • Cameron Paterson provides a useful introduction to Ron Ritchhart’s Cultures of Thinking and the notion of documentation. Along with Silvia Tolisano and Diane Kashin, I have written about Project Zero and the routines of thinking before. I was also left thinking about the power of documentation during a recent session with Amy Burvall, where we critiqued our creative thinking. However, Cameron’s post also left me wondering about the place of thinking and documentation outside of the classroom?
    Liked Sometimes They Come Back by Jim Groom (bavatuesdays)
    Documenting my work on this blog has basically defined my career. There is no way I would have remembered this assignment, no less gotten kudos from strangers more than a decade later, if I hadn’t taken the time to blog it. I am increasingly convinced that blogging is a long-term investment in your soul, and this is the most recent dividend.
    Bookmarked API Life Cycle Basics: Documentation (apievangelist.com)
    API documentation should not be static. It should always be driven from OpenAPI, JSON Schema, and other pipeline artifacts. Documentation should be part of the CI/CD build process, and published as part of an API portal life cycle as mentioned above. API documentation should exist for ALL APIs that are deployed within an organization, and used to drive conversations across development as well as business groups–making sure the details of API design are always in as plain language as possible.
    Kin Lane as the API Evangelist on the importance of documentation, this is a part of his work on API Basics