Updates

niemasd · May 14, 2024 · 9aeca41 · 9aeca41
1 parent 6758333
commit 9aeca41
Show file tree

Hide file tree

Showing 4 changed files with 26 additions and 3 deletions.
diff --git a/images/google_calendar_lab_hours.png b/images/google_calendar_lab_hours.png
diff --git a/images/google_calendar_main.png b/images/google_calendar_main.png
diff --git a/teach_online/example.md b/teach_online/example.md
@@ -240,14 +240,30 @@ but you can read about my exam similarity detection methods in the
 (niemas-example-course-google-calendar)=
 ## Course Calendar: Google Calendar
 
-For keeping track of course sessions, assessment release dates, and deadlines,
+For keeping track of important course-related dates,
 I like to use [Google Calendar](https://calendar.google.com).
 I typically create two calendars:
-one "main" calendar that has the items described above,
-and a second "office hours" calendar that has all office hours for all members of the instructional staff.
+
+1. A "main" calendar that contains synchronous class sessions, instructor and graduate TA office hours, release dates, deadlines, and exams ({numref}`google_calendar_main`)
+2. A "lab hours" calendar that has all drop-in office hours that are held by undergraduate instructional assistants (Tutors) rather than instructors/TAs ({numref}`google_calendar_lab_hours`)
+
 I like to use Google Calendar because it's easy to manage, share, and embed,
 and students can easily subscribe to the Google Calendar and have it sync with their laptop, phone, tablet, etc.
 
+```{figure} ../images/google_calendar_main.png
+---
+name: google_calendar_main
+---
+Main calendar from an example *Advanced Data Structures* course.
+```
+
+```{figure} ../images/google_calendar_lab_hours.png
+---
+name: google_calendar_lab_hours
+---
+Lab Hours calendar from an example *Advanced Data Structures* course.
+```
+
 (niemas-example-course-canvas)=
 ## Gradebook: Canvas
 

diff --git a/teach_online/general_tips.md b/teach_online/general_tips.md
@@ -101,6 +101,13 @@ Thus, my general tip is to try to reduce {term}`Technology Fatigue`:
 * When possible, try to have a single "main" technology/website that students can bookmark, and seamlessly *embed* other technologies *within* it
   * Try to avoid manual interaction on the student's end when at all possible
 
+(general-tips-automate-everything)=
+## Automate EVERYTHING!
+
+I'm not sure if this should be a [Spicy Take](#niemas-spicy-takes) instead of a [General Tip](#general-tips),
+but I think it's not quite spicy enough, so I'll leave it here.
+TODO
+
 (general-tips-glossary)=
 ## Glossary