Week 2 slides cover too many topics

[franzknupfer]

Currently, the week 2 slides cover the following topics:

• Definitions of DEI
• Why DEI is important
• Systemic inequality in tech industry
• Privilege
• Imposter syndrome

This is content for multiple talks. The current lesson just covers equity vs equality and privilege. I think that would be enough for the talk. To be honest, even those should probably be separate lessons since they are separate topics.

I definitely think imposter syndrome should have its own talk. If possible, each talk should really drill down on one topic instead of trying to cover too much at once. Otherwise, the lessons will get too broad.

[remy-says-hi]

I agree! I think it should be split up as follows:

1. Intro
   • definitions of DEI,
   • talk about Epicodus's committement
   • how students are from vastly different backgrounds
   • the very real challenges of pair programming,
   • the to-dos of pair programming to practice inclusion
2. Why DEI is important
   • companies value diversity
   • they want to get a job,
   • soft skills are going to be the biggest thing they are hired on,
   • A check in on pair-programming - how is it going, what helps, what doesn't help.

Week 3 would cover microagressions, and week 4 would cover systemic inequalities, privilege and imposter syndrome. Would week 4 then be a bit too much?

[franzknupfer]

I think that would be too much content to put in one week 4 lesson but I can add a separate lesson on imposter syndrome. I think it's okay if the standup covers multiple topics - it just might mean several lessons for students the night before.

As I stated in my email, here are the weeks that I think should be split into multiple topics:

• week 2: importance of DEI / pair programming check-in - very different topics - what is the pair programming check-in exactly? A forum for students to discuss things that are coming up? If so, I'd say that's separate than a DEI topic and maybe it would be good to have it as a separate discussion that week. It's also fine to keep them combined. I could add a brief lesson about pair programming in general asking students to self-analyze their experience, but I'm inclined not to have that lesson in the next cohort.
• week 4: Recognizing privilege / Imposter syndrome: I'm happy to write up a lesson on imposter syndrome and then they'd read both lessons on privilege and imposter syndrome. Does that sound okay?
• week 7: I'm inclined to separate signal boosting and issues with cliques into two different topics - I'll have to look over the content, though.

[franzknupfer]

As of now, here are the lessons that correspond to topics. We have drafts of the first five weeks complete. The list here is necessary because they are currently in a different order - want to make sure that this lines up okay before I change the order.

Week 1: https://github.com/epicodus-classroom/dei-curriculum/blob/master/dei-talks/0_intro_to_dei_talks.md Week 2: https://github.com/epicodus-classroom/dei-curriculum/blob/master/dei-talks/1_why_dei_is_important.md Week 3: https://github.com/epicodus-classroom/dei-curriculum/blob/master/dei-talks/3_identifying_and_preventing_microaggressions.md Week 4: https://github.com/epicodus-classroom/dei-curriculum/blob/master/dei-talks/2_recognizing_privilege.md Week 5: https://github.com/epicodus-classroom/dei-curriculum/blob/master/dei-talks/4_asking_and_listening.md

[franzknupfer]

I've drafted a lesson on imposter syndrome: https://github.com/epicodus-classroom/dei-curriculum/blob/master/dei-talks/1_imposter_syndrome.md. We can potentially have two lessons the week of recognizing privilege, with an additional lesson on imposter syndrome - though personally, I'd like to keep the once a week cadence if possible!