Link to my Job Search Plan Details
Design a 40-hour "work week" that provides time for:
| # Feedback III Reflection | |
| * What are you doing well as a pair programmer and collaborator? | |
| I am good at reading my partners and knowing when they are struggling, and responding to that with a project or pairing strategy pivot. | |
| I am good at adapting to my partners needs. I am good at setting a clear direction and organizing the project. I am good at addressing | |
| areas in which my partner needs a bit of help with understanding. | |
| * How do you use your strengths as a team member? | |
| I am quite strategic in my approach to organizing the project and delegating work. I use my developer strength to challenge my partners to | |
| level up in their coding skills. I use empathy to stay present with my partner and respond to anything that isn't working out for them. |
| # Feedback II Reflection | |
| * Date of feedback conversation: 08/24/2017 | |
| * How did you prepare for the conversation? | |
| I made notes about what my partner did well and how he most contributed to the project as well as areas he could improve and actionable steps he could take. | |
| * How did the conversation go for you? What was easy about the conversation? What was more difficult? | |
| The conversation was comfortable and easy. We had been providing feedback to each other throughout the project and had a mid-project DTR, so there were no surprises. I wish he had more feedback for me. |
| # Agile Project Management | |
| * What project management strategies did you use in your projects this module? | |
| I tried to value my partners over the processes by adapting to their specific needs and strengths in the project. | |
| I valued their and my own learning experience over having a perfect project. | |
| I focused on figuring out a working project on my own path vs. forcing solutions because they seemed like the 'correct' solutions. | |
| I tried to remain flexible to re-evaluate our projected path at anytime and be ready to pivot if we needed to go in a different direction. | |
| * What went well? | |
| In gametime, Hector was able to learn more from the project because I prompted a pivot of out pairing strategy when it proved to be unproductive. |
| # Cold Outreach I Deliverable: | |
| * Name of contact | |
| * The mentor (or alum) I contacted is Mary Beth Burch. | |
| * Date of contact | |
| * 08/24/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?) |
| The MIT License (MIT) | |
| Copyright (c) 2015 Justin Perry | |
| Permission is hereby granted, free of charge, to any person obtaining a copy of | |
| this software and associated documentation files (the "Software"), to deal in | |
| the Software without restriction, including without limitation the rights to | |
| use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of | |
| the Software, and to permit persons to whom the Software is furnished to do so, | |
| subject to the following conditions: |
| Project: Idea Box | |
| Group Member Names: Lola Brenner, Erik Ingvalson | |
| Project Expectations: What does each group member hope to get out of this project? Better understanding of jQuery and local storage, overcoming differences in work habits (introvert v extrovert), seamless communication | |
| Goals and expectations: github mastery, lots of commits on github, smooth workflow with ping-pong style, use lots of jQuery | |
| Team strengths: communication skills, asking for help, code organization, improving CSS skills, pseudocoding |
| Project: Idea Box | |
| Group Member Names: Lola Brenner, Erik Ingvalson | |
| Project Expectations: What does each group member hope to get out of this project? Better understanding of jQuery and local storage, overcoming differences in work habits (introvert v extrovert), seamless communication | |
| Goals and expectations: github mastery, lots of commits on github, smooth workflow with ping-pong style, use lots of jQuery | |
| Team strengths: communication skills, asking for help, code organization, improving CSS skills, pseudocoding |
| # Commitments for Accessibility | |
| 1. making use of tabindex and semantic html | |
| 2. using the Axe Chrome extension to analyze the accessibility of my apps | |
| 3. use alt text for all my images |
