mschae16

To prepare for the Docker 101 workshop, please install Docker and follow the steps in creating a Dockerhub account.

To prepare for the Kubernetes 101 workshop, please install the following:

• Docker
• minikube

Verify your minikube install by running the following commands in your terminal:

$ minikube start and

mschae16

Use these rapid keyboard shortcuts to control the GitHub Atom text editor on Mac OSX.

Key to the Keys

• ⌘ : Command key
• ⌃ : Control key
• ⌫ : Delete key
• ← : Left arrow key
• → : Right arrow key
• ↑ : Up arrow key

mschae16

Post-Grad Job Search Action Plan Template: Your first 30 Days

You are so close! You've spent the last 7 months working towards this -- graduation and finding your new dream job! This plan is meant to help you streamline your goals and get on the path to employment as a software developer during the first 30 days after graduation. Please fill out the plan by copying this template into a gist to submit in your portfolio.

As you fill out this plan, consider how your first job search will set the tone for your career trajectory in the software industry. After all, your first developer job should align with those goals as well so that you're on track for a longterm successful career.

Note: If you have already secured a job prior to graduation, skip to the second part of the plan below.

#1: 30-Day Job Search Action Plan

Create a schedule & goals for the first 30 days Post-Graduation

mschae16

Template: Module 4 Action Plan

Module 4 Goals

• Have started the job search, but is not necessary to have a job by end of mod 4
• Would like to be in contact/meeting up with several contacts in the industry
• Have a thorough understanding of technologies on the back-end
• Focus on learning throughout mod 4 over gaining employment

Strategy To Achieve Goals:

In this section, break down your longterm goal into smaller goals that you want to work on each week and/or day

mschae16

Flower Exercise

My Favorite People to Work With

• Team players
• Mentors
• People with confidence
• People who are straightforward and direct
• People who don't cause drama
• People who are open to sharing new ideas and contribute
• Honest people

mschae16

Microaggressions

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

I have not really experienced microaggressions in my time at Turing, other than one instance, when a fellow student in another module was explaining some code to a group of us (two females and one male), and was clearly directing his speech at the one male of the group, with his back generally turned towards us. In life, I am often asked where I come from, have been told I look 'exotic', 'different', asked if I speak Spanish, and by my general vocal volume level, been assumed to be a loud American.

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

Sometimes, I simply ignore them. Others, I reply with a statement directly addressing whatever was said, to make sure the other person is aware of the offense.

mschae16

Write: Reflect on your experience at Turing thus far and write out your story, answering the questions who are you, why are you here, what's next? Think about how others might root for you as a character and what's at stake for you in your career transition. Consider:

Your Strengths: what makes you the "hero" of this story? If you took StrengthsFinder, reflect on how developing your strengths at Turing has influenced your story How have you grown at Turing? What obstacles have you overcome? What turning points led you to make this career change? What does your third act look like? How does transitioning to this career bring some closure to this narrative arc? Describe causality -- what made you want to make this career change? How is it grounded in your character? How you can create trust with the listener Creating coherence in your story

mschae16

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

This mod, in both my Game-time project and my Weathrly project, my project partner and I are organizing our task assignments using waffle (kanban board) in order to ensure that we both do not accidentally work on the same feature. Before each project, my partner and I would sit down and have a DTR in order to decide on our optimal work schedules, and what works best for each person regarding our strengths, skills, and areas we need improvement on.

What went well?

In Game-time, my partner and I kept to a schedule on time-boxing our pairing sessions, and switching driver/navigator during our pairings. We also realized that planning our strategy via whiteboarding prior to actually sitting down and writing our code really helped to speed up the process for both of us and as a result, both of us not only understood the logic behind solutions in much more depth, but we were able to get through writing the code faster.

Wha

mschae16

Feedback III Reflection

• What are you doing well as a pair programmer and collaborator? How do you use your strengths as a team member?

  • As a pair programmer and collaborator, both my teammates and I feel that my strengths lie in my open and honest communication with others. I collaborate well in that I am responsible and dependable, hold myself accountable both to myself and my team members, and am also flexible enough to facilitate a smooth and fluid relationship with others. I feel I am an assertive person by nature, which I definitely espouse in my pairings, but my adaptability helps to allow for accepting others' opinions and strategies over my own if for the most positive outcome and benefit of the team.

• How would you like to continue to develop your strengths?

• I would definitely like to continue to capitalise on my learner mentality in that I think my desire and need to understand processes behind the way in which things operate (essentially the "why" question) can only serve to rei

mschae16

Feedback II Reflection

• Date of feedback conversation: July 18, 2017

• How did you prepare for the conversation?

  • During my time working with Laura Caroselli on our Game-time project, I consistently made an effort to note down any feedback I had for our time pairing together and later compiled my notes into a written paragraph, which I then brought with me to our conversation as documented evidence. Having the notes to refer to made the conversation very easy in that I had very clear and specific instances to allude to. I also made sure to schedule our conversation for a time and date that was convenient to both of us, and also to make sure we were both in a good head space to have this dialogue.

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