Group Members: Michael Gallup, Antonio Jackson, Jesse Gietzen, John Watterson, Charles Wefso
- Michael Gallup:
- Antonio Jackson: 10 am - 3 pm time preference, Tues & Thurs day preference
- Jesse Gietzen: any time during normal waking hours, no day preferences
- John Watterson:
- Charles Wefso: 9 am - 5 pm preference. Tues and Thurs sound good to me, but I’m very open.
What do we want to work on together for technical practice? Suggestions: group code challenges/project work/code reviews
- Michael Gallup:
- Antonio Jackson: I’m open to full stack group projects, not really interested in code challenges or code reviews
- Jesse Gietzen: CI, authentication, apps written in python and/or c#
- John Watterson:
- Charles Wefso: I have several Turing projects I would like to rebuild from scratch. I could always use another set of eyes and the occasional person to bounce ideas off of. Not super into code challenges.
- Michael Gallup:
- Antonio Jackson: Check Ins during our meetings
- Jesse Gietzen: check ins seems like a good time to do this
- John Watterson:
- Charles Wefso: Check ins and reaching out if we haven’t heard from each other in a while. Just keeping up communication.
Group member strengths for supporting each other in the job search (what can we each help our group with?):
- Michael Gallup:
- Antonio Jackson: Emotional support
- Jesse Gietzen: interview practice, emotional support, maybe code stuff
- John Watterson:
- Charles Wefso: People to commiserate with and celebrate wins.
- Michael Gallup:
- Antonio Jackson: Nada
- Jesse Gietzen: i’m not sure yet. my brain is still full
- John Watterson:
- Charles Wefso: Sleep. Don’t bother me while I sleep.
- Michael Gallup:
- Antonio Jackson: We can check in on action steps during our meetings and slack the group if we need to miss a meeting. I think the five repeating weekly questions from the Mod 4 career journal would be good to go over at our meetings.
- Jesse Gietzen: i like the career journal approach, as well
- John Watterson:
- Charles Wefso: A agree with Antonio. We should use those five questions as an outline but try to keep the check-ins light and short. If we haven’t heard from someone reach out.
Create a calendar.