Why! Why! Do I receive emails daily from my students which state: “Sorry for bothering you…” or “I apologize for the email...". Are you kidding me? What kind of student culture are we as a system and as educators developing where students feel like a question is an imposition.
Don't get me wrong, I recognize that many of our inboxes r overflowing with messages. Though that is MORE likely the result of your bad email management than overwhelm by student questions (yes I know, admin emails too). If we are not there to guide the prepared and uprepared…
students alike, what the hell are you doing in this profession. A tangential analogy perhaps. I was a chef for a decade. A far too many chefs I met were upset when customers wished to modify a dish to remove this or add this, or make some kind of exception. While recipe integrity
is a real issue, why get upset about modifications. Aren't you there to serve your customers. This is similar to when a customer complains about a dish. Why get mad… It is either you didn't do it right OR the customer has different expectations. Either way, flexibility is req.
My students deserve my attention, even in email. Though I really don't promise immediate responses or even responses on the weekends (we have lives too), there will be a thoughtful response. What are we doing to create this kind of culture?
• • •
Missing some Tweet in this thread? You can try to
force a refresh
My PKM journey has been one of significant pedagogical trials and tribulations. I detailed much of it here: roambrain.com/roaming-in-the…
The TL:DR - it began as a search for a single tool to manage my pedagogical development as a college instructor and the curriculum I was developing for the 6 courses that I taught.
#AdviceFromARoman Continuing the "advice" column that I started some time back regarding how to best utilize @RoamResearch for your knowledge graph. The TL:DR, every block or block-tree should have three elements associated with it. An ENTITY, a TYPE, and of course its CONTENT.
What do I mean? Fundamentally, Roam "search" is a very different paradigm than other consumer writing/notes applications. Well, I am not going to explain how Roam works behind referring to my prior advice tweets about tag/page ref inheritance.
Importantly though, exploiting Roam's search workflow requires you to recognize that the power is in page refs (and "tags"). But because Roam is so flexible to the point of being agnostic in this regard, one must build with search and discoverability in mind.
A word of advice #Roamans. One of the great virtues of @RoamResearch is its flexibility and efficiency in capturing the chaos of life. Yet one of its largest hinderances to its success as a tool is its users’ behavior. There are several ways that we might better manage our graph.
One such way is to avoid page ref clutter. Two strategies. First, if you use templates (particularly daily), and you don’t end up capturing anything under a page ref - **delete it** - it will only clutter your graph, query results, and contribute to page bloat.
Similarly, if you use {{queries}} on your daily page - **delete** them as a shut-down routine. They are pointless beyond the day at which you use them. Or, as I have done, create a dashboard page containing the desired queries and use #roam42 SmartBlocks to dynamically update.
#RoamCult For new users who are like, "why is building a table or Kanban board so odd?" They are designed to take advantage of @RoamResearch's hierarchical relationships. Cells in a table row and Cards in a Kanban column are related. Use that to your advantage.
For example. Take a table. You can query for example for any value {a, b, c, d} in relation to "Item 1" since they are in the same hierarchy.
Similarly, for a Kanban Board - though constructing one is different {a, b, c, d} are still related to "Item 1." HOWEVER, as an advantage, in a Kanban board, block "a" is NOT related to block "b" outside of that fact that they share a parent.