CSC 322.01, Class 05: Initial team meetings
Overview
- Preliminaries
- Notes and news
- Upcoming work
- Extra credit
- Questions
- Setting the stage
- Quick introductions
- Team résumé reviews
- Group debrief
Preliminaries
Notes and news
Upcoming work
- Identify strengths and roles due Thursday at 8:00pm.
Good things to do: Academic
- CS Table and Extras
Good things to do: Miscellaneous
- Women in Computing Thursday at 6pm in CS Commons.
- Trustees are in town Thursday-Saturday, if you have a chance to meet with them, consider using it.
Questions
Setting the stage
- Better teams start by learning about each other.
- We’ll need to decide on primary roles.
- Part of your broader professional development.
Quick introductions
- Introduce yourselves to your teammates.
Team résumé reviews
- Read your peers’ résumés.
- Discuss the following issues:
- If I knew nothing else about this person, what would I think about how they would contribute to my team?
- What is something I’d like to adapt from their résumé?
- What is something they should change on their résumé?
- Plan to finish by about 3:35.
Group debrief
Note
- It can be hard to look at these and say “I don’t look as good on paper.”
- But you are all great.
- Disclaimer: There’s a lot of disagreement about what makes a good technical resume.
What did you learn?
- LaTeX can make pretty resumes.
- “Wow, this person claims to be technical but they don’t know
how to separate their technical and non-technical experience.”
- Think about different resumes for different situations
- Not everything needs to be on your resume.
- People perceive me differently from my resume than I would want to be perceived.
- Legibility is important.
- How do you show off important things like leadership when they come from non-technical experiences.