Skip to content

Instantly share code, notes, and snippets.

@kevinkrom787
Last active April 16, 2018 01:26
Show Gist options
  • Save kevinkrom787/8ccb9a64eabfe0e6c67778c50849e855 to your computer and use it in GitHub Desktop.
Save kevinkrom787/8ccb9a64eabfe0e6c67778c50849e855 to your computer and use it in GitHub Desktop.

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?

  • The main strengths I'm going to focus on are problem solving and adaptability. While I’ve never considered myself a problem solver in the traditional sense, I’ve started seeing patterns of problem solving in my previous career and it opened my eyes to the fact that I’ve been problem solving my entire life. The area that I need to focus on is boiling problems down into their most fundamental properties and then starting to solve from there. The biggest thing I’ve learned is I need to spend a lot more time understanding the problem that I’m looking to solve. As far as how my understanding of this has changed, it’d have to be that problem solving isn’t just getting the right answer. It’s about fully understanding every step in the process to get from problem to solution and being able to speak to it! Adaptability was another strength I was given and this is one I’ve always held near and dear to my heart. I’ve seen this the most when working with partners at Turing. You’re always going to be working with others in life and being able to adapt to their learning and working style is incredibly beneficial. Some people want to work through problems alone and it’s my responsibility to read that (or discuss that in the DTR!) and create an environment that works for both parties. The biggest takeaway from Turing regarding adaptability is that there are a million ways to do something in software development. You’ve just gotta find the way that makes the most sense to you.

Write a story about your Turing experience so far: When have you struggled? How have you dealt with struggle? When have you succeeded at Turing? How did you accomplish those successes?

  • Turing has been the most challenging and yet most rewarding experience of my life thus far. My educational experience to this point was to avoid the classes that I wasn’t inherently good at and focus on those that came easily. Turns out, logic and coding don’t come easily but I’m finding myself excited to learn challenging concepts and push myself past my fixed mindset. I struggle every day but there are also a number of little victories that keep me going. The best practice for overcoming strife is to talk with others who are going through what you’re dealing with. Learn from them and find ways to make it through! One example of a big victory came from Mythical-Creatures. When I started it, I was completely overwhelmed and didn’t understand a thing. I made a plan to go home and practice pretty much every night and now people are coming to me for help. Feels pretty good to help others in an area where I felt like I was going to fail.

After you practice storytelling in the session, answer this question: What was particularly easy or difficult about telling your story? What are 1-2 steps that you can take to continue to improve your abilities to tell your story, talk about yourself with ease, and examine your strengths?

  • It’s easy to talk about your victories in your past career. I found myself learning on arbitrary accomplishments that I was trying to compare to strengths in the field of software development. One way to improve is to get out there and give it a shot at networking events! You’ll automatically become more comfortable with practice and it’ll get you comfortable talking about why you’re becoming a developer along with what motivates you. Another way to improve is to key in on your values and continually bring your story back to those values. It also helps if you get lost in an interview, you have something to come back to!
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment