[Challenge 1] (http://codepen.io/tlgreg86/pen/egVvde)
[Challenge 2] (http://codepen.io/tlgreg86/pen/vgdxyw)
[Challenge 3] (http://codepen.io/tlgreg86/pen/EZQmPz)
[Challenge 4] (http://codepen.io/tlgreg86/pen/ggvqXR)
[Challenge 5] (http://codepen.io/tlgreg86/pen/ygvwBW)
* Comin atcya perpetually live! The Turing Podcast! Today:
incl. some tid-bits from current students
* M1 BE-
* M1 FE- Till Now: HTML, CSS, Javascript, JQuery,
W4: JSON (JavaScript Object Notation) and local storage, Ideabox (Similar to linked list in functionality but will utilize JQuery and JSON as well as local storage), Static Comp #2
| Name of contact | |
| - The mentor I contacted is Weston Miller. He isn't a Turing mentor but he does work in the tech indurstry locally. | |
| Date of contact | |
| - 03/16/2017 | |
| - Since reaching out to Weston, we have met in person almost every thursday since 3/16 as well as several remote pairing sessions over ScreenHero. We generally work on coding challenges but also work on project material as well. As of right now we are planning on pairing over the intermission on 4/27. |
| Throughout this mod I've tried applying agile practies to my projects with some success. I have found that if I develope small pieces of functionality, test that piece, and once functional commit that piece, my end work has fewer bugs and I spend less time on the back end of the project hunting bugs. In the instances where I struggle with creating a piece of functionality I seudo code what I'm thinking rather than write bad code in hopes of coming up with a solution. This has also helped streamline my projects. |
| How did you prepare for the conversation? | |
| We learned in this session that with redards to your feedback, what you meant to say and how what you said is interpreted can be very different things. I prepared for this conversation by thinking about the feedback that I want to give and then I went another level deeper and thought about how to more effectively communicate that feedback in such a way that it isn't misconstrued. | |
| How did the conversation go for you? What was easy about the conversation? What was more difficult? | |
| When I finally had the feedback conversation with my partner things went really well. I had thought through the feedback I was going to give and because of that I was able to convey it without issue. The easiest part of the conversation was giving the positive feedback for the obvious reason that it had no potential to be hurful or taken personally. The difficult part was giving the critical feedback. | |
| What principles of feedback did you use in the conversation? |
| What are you doing well as a pair programmer and collaborator? | |
| With regards to pairing and collaborating on projects, I think my communication and planning skills make me a great partner/team member. | |
| How do you use your strengths as a team member? | |
| I often times find that my affinity towards planning is a strength in a team environment because the planning portion of projects can be the most difficult and when done well can make things move much more smoothly. | |
| How would you like to continue to develop your strengths? |
| How have you experienced microagressions in your time at Turing or in your life? | |
| Being from Kentucky and from Hispanic heritage I frequently encounter microagressions whether at Turing or in my daily life. Many times the first thing people say to me is do I speak spanish, do I wear shoes, and where's your accent? This always bugs me because it makes me feel out of place where I'm at and like I'm perceived as a bumpkin. |