To all those educators out there. Get to know your students, BUT hear them as well. I ask students at the end to share there thoughts about their experience in my course and what I have taught. EVERY SEMESTER is enlightening. Who they are. Their struggles. Their triumphs. 1/3 👇
The amazing perspective that individuals have, that is often suppressed in an educational setting is startling. A pedagogy that does not acknowledge these facts is borderline oppressive. 2/3
Over the last couple years I look back at their responses, the positive and the negative, to reflect on my own progress. Perhaps more importantly, & selfishly, to gain fuel for the struggle in the future. Teaching history is often not "respected”/acknowledged as valuable. 3/3
Sometimes it is appropriate to recognize that the future is more than what is on display. The future is more than can be seen from the present. #SummerReflection #Pedagogy 4/3

• • •

Missing some Tweet in this thread? You can try to force a refresh

Keep Current with Calhist𐃏rian

Calhist𐃏rian Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!


Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @calhistorian

Nov 18, 2021
Its been 2 years now since I began using Roam regularly... quite remarkable frankly. #roam #TFT
My PKM journey has been one of significant pedagogical trials and tribulations. I detailed much of it here:…
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.
Read 20 tweets
Jul 16, 2021
#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.
Read 7 tweets
Jun 14, 2021
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.
Read 11 tweets
Jan 30, 2021
#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.
Read 5 tweets
Jan 4, 2021
#RoamCult if you ever thought Roam could not be used for a Weekly Review GTD style, it just requires Roamafying the workflow. Most data is removed or collapsed for privacy. Though #roam42 (@roamhacker) SmartBlocks are required. Doing this manually every week would be too much
This was just me finalizing from my old Weekly Review model:
Thanks @Conaw . Truly a tool that CAN do anything you want it to within the specific affordances and constraints.
Read 6 tweets

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!


0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy


3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!