| How have you changed since you started at Turing? How have your strengths helped you in that progress? | |
| More accutely aware of my shortcomings and what I need to work on. Knowing that Adaptability can be a double edged sword when I can't say no to people helped bring that aspect of my issues into focus. | |
| How do you feel like you have used your strengths when you've paired with others? | |
| When others might get bogged down in the minutia of trying to step through a problem I usually have been able to push us through it stratigically someway. I also have tended to lead every pairing, build out waffle and set expectations for milestone completion and general workflow. Also, refactoring comes easier to me as well as discovering and fixing bugs. | |
| How could you utilize these strengths more? | |
| I think I should continue to push to take more of a leadership role and continue to get comfortable directing the management of a project. |
| Feedback II Reflection | |
| Date of feedback conversation: Around the time of the session instructing us to complete this deliverable | |
| How did you prepare for the conversation? | |
| No prep really, I think we are both pretty well aware of our shortcomings and there was much that was going to be said that we weren't already somewhat aware of. We also had a number of personal discussions during the course of the project that made us more comfortable with eachother to begin with. | |
| How did the conversation go for you? What was easy about the conversation? What was more difficult? | |
| Turns out we used a sort of agile practice in Game Time. Instead of wading through the project trying to account for every little thing, we shot immediately for a working product that we could then refactor and itterate on to get it to where we want. We paired on the initial implementation then I handled refactoring mostly and Adam handled the testing. |
| Documentation Guidelines for Cold Outreach I Deliverable: | |
| Name of contact | |
| "The mentor (or alum) I contacted is Daniel Glauser" | |
| Date of contact | |
| "08/16/2017" |
| Project: 2DoBox | |
| Group Member Names: Ben Porter & David Ryan | |
| Project Expectations: What does each group member hope to get out of this project? | |
| Goals and expectations: Solidifying our understanding of the material through exposure to another codebase. Utilizing kanban boarding to organize the project and distribute workload as well as enhance the ability to work remotely. | |
| Team strengths: Both strong logic skills with some previous familiarity of programming. Strong communication. Willingness to adapt. |
| Where I am - I've been successfully using semantic HTML and have tried to incorporate roles as well. | |
| Where I want to be - I think I'd like to investigate how to better utilize tab indexing and help the visually impaired. |
| Strengths & Storytelling Reflection Guidelines | |
| Build on your professional story by thinking about how you're progressing at Turing. Answer the questions below in your own gist to use your StrengthsFinder themes to add to your story: | |
| Write 1-2 paragraphs about your StrengthsFinder themes: How have you seen yourself using these strengths at Turing? Has your understanding of these strengths changed since you first reflected on them? If so, how? | |
| A collector of facts, obsessed with the distilation of ideas, a thinker, a learner and adaptable. I see this helping me at turing when the time comes for the really conceptually difficult leasons. My ability to absorb these ideas and then distill them for others might prove invaluable in my cohort. However the caveats here are my tendancy to get bored once i understand a subject and no longer feel challenged by it, or how adaptability can also mean I have a hard time setting boundries with others and telling them no. I have to be careful to not spread myself to |
Strengths: Resourcefulness, refactoring, planning
How to work with someone else: Be highly involved in the planning/draft process to avoid pitfalls. Get the big pieces out of the way so we can focuso n finer details and features.
Communication: Just being clear on expectations
Workflow: Ping-pong, division of features
Dif Person: Just establish process and expectations
Description of approach // this is a paragraph is Markdown Challenge number // this is a link in Markdown.
| **Directions:** Copy this template into your own gist. | |
| # Strengths Reflection & Coaching Request | |
| ### Read Through Your Theme Definitions | |
| 1. What words or phrases stick out to you? How would you define each of your top 5 talents in your own words? | |