the-oem

Keybase proof

I hereby claim:

• I am the-oem on github.
• I am oem (https://keybase.io/oem) on keybase.
• I have a public key ASCSlNZYoSLhVkr3NtO9jNzDmJFR7Io-3Vo-rhtb4RUgBwo

To claim this, I am signing this object:

the-oem

Title

<Additional information about your API call. Try to use verbs that match both request type (fetching vs modifying) and plurality (one vs multiple).>

• URL

  <The URL Structure (path only, no root url)>

• Method:

the-oem

How have you experienced microagressions in your time at Turing or in your life?

• I have quite a few years of tech experience and I have often felt like people view that and don't think I should be here. This has come in the form of students here, as well as from people outside of Turing that come to learn that I'm actually going through the program as a student rather than being part of Turing as an employee.

What ways have you been able to address microagressions that you have seen happen?

• I always address it head on, and correct people, usually through sharing my story (there's that thing again where we need to be able to tell our story.)

What role could you play in interupting microagressions for others?

• Many examples from the articles are also things that I might unconsciously find myself saying, without intending to hurt someone. I could definitely spend time being more aware of the micro-aggressions happening and speak up, teaching people to think first before they speak.

the-oem

Agile Practices Reflection

What project management strategies did you use in your projects this module?

• We used a variety of strategies, namely working towards a MVP (minimum viable product) and breaking the work up into smaller, more easily digestible chunks of work. We leveraged Waffle.io to track work and bring visibility to the work in progress, and to also keep new work organized as it was discovered.

What went well?

• Getting visibility went well, especially during times when we weren't able to pair side-by-side. This allowed us to see what needed to be done and work collaboratively even when remote. We definitely were able to work on getting a each phase done in sequence and deliver what felt like a good MVP.

the-oem

What are you doing well as a pair programmer and collaborator?

• I feel like I am doing very well with my communication and collaboration. Because I've been in the industry in the past, I definitely understand the benefits of these things. I also think I am doing well with teaching/mentoring my partners in areas where I am stronger.

How do you use your strengths as a team member?

• Woo - I used this quite often to calm people down and reduce stress.
• Communication - This is another strength I use quite heavily with others. Because we are working with others in such close quarters and sometimes under a great deal of stress, communication is key to collaboration.

How would you like to continue to develop your strengths?

• I think Futuristic is definitely a strength I could utilize more often. I tend to get sucked down into whatever is happening at the moment during school that I sometimes forget to be forward thinking about things.

the-oem

Name of contact

• The mentor (or alum) I contacted is Micah Adams.

Date of contact

• "03/15/2017"

Outcome (i.e., did you get a response? If not, what is your follow-up plan? Did you meet? When? What was the result?)

• Micah responded, and has been helping me as needed throughout module 1 and module 2. I was fortunate in that Micah used to work for me in the past, so we already had a great working relationship.

How do you feel like this relationship will benefit you in your longterm professional development?

the-oem

Feedback II Reflection (for Evan Miller, my project partner on Game Time)

• Date of feedback conversation: May 10, 2017

• How did you prepare for the conversation? I spent time during our GearUp session reflecting on the project and how it's been going. For me, I think the feedback that I want to give Evan also applies to myself. More often than not, we both seemed to prefer working solo and checking in with one another, rather than truly practicing pair-programming.

• How did the conversation go for you? What was easy about the conversation? What was more difficult?

the-oem

0. You got this

Embrace mistakes -- cmd+alt+j add console log everything

Ask questions and help each other

Get as much Javascript practice as you can -- start early, slay often.

Pin things on Slack

Pre-read, re-read

Mythical Creatures - pair,

Rely on the support systems

Stick together

Be kind to yourself --- acknowledge the progress you have made

the-oem

Examples of Law of Closure being used in company logos.

the-oem

Template for DTR Memo

Project: 2DoBox Pivot (Mod 1, FEE)

Group Member Names: Jason Collins & Kristi Green

Project Expectations: What does each group member hope to get out of this project?

• Kristi: wants to learn how to refactor efficiently and learn more about the functionality of the application
• Jason: implementing more array prototypes, based on feedback in last eval