cbdallavalle/Strengths & Storytelling

## Strengths & Storytelling
1. Learner, input, activator, restorator. I have been using my learning and restorator strengths consistently during mod1. I am an avid learner and often thrive in environments like Turing where I learn something new every day. Even though the lessons and projects can be overwhelming at times, my love to solve problems and the energy I receive from challenges keeps me going. When I first took the strengths finder, I was not sure how much input was a part of my persionality. I did not identify with being a collector, in fact, all throughout my childhood the only thing I collected were dirty clothes on my bedroom floor. As I spent more time at Turing, I realized that I do collect information, though. I often log away in my brain different facts from lecture and my own independent study to use later in my code. I also store tidbits of information about other people and use them later in our interactions. I have seen aspects of my strengths play out while at Turing, and I now recgonize those strengths and capitilize on them when I can.

2. I came to Turing because I was not happy in the career path I had chosen, but I was still not entirely convinced that I was going to love learning software development. I thought this was a good opportunity for me to become a more employable worker and if I didn't want to do development as a career, I'd work for a couple of years to pay off the tuition and I could try another career. After 4 weeks of lectures, projects, independent study, and being a part of the Turing community, I am certain I want to pursue a career in software development, which is very exciting! I have definitely had my highs and lows at Turing. I have gotten better at recognizing when I am at a low, and taking breaks and providing myself sufficient care to get me back on track. When I have successes at Turing, they spur me forward to learn and grow more.

3. I don't exactly know what I want my future outside of Turing to be. There many directions software development can take me, so I want to at least experience the industry before I make a decision about what sort of career I want to pursue. My goal after Turing is to get a few years of experience working in the industry, so I can connect with the community and start discovering different career paths. I would also like to see what opportunities the conservation field may have for software developers.

4. The most difficult part is sharing my future vision. I am young and Turing was and is my introduction into the coding industry. Because of that, I just don't know where I want my career to take me. I see this as an issue future employers may have with me, since they might interpret my indecision as a lack of motivation and drive. I think to improve this aspect of my story, I can start to connect myself more with the tech industry here in Denver. I should meet with mentors to discuss the different career paths available and reach out to people in those areas to find out more.
	1. Learner, input, activator, restorator. I have been using my learning and restorator strengths consistently during mod1. I am an avid learner and often thrive in environments like Turing where I learn something new every day. Even though the lessons and projects can be overwhelming at times, my love to solve problems and the energy I receive from challenges keeps me going. When I first took the strengths finder, I was not sure how much input was a part of my persionality. I did not identify with being a collector, in fact, all throughout my childhood the only thing I collected were dirty clothes on my bedroom floor. As I spent more time at Turing, I realized that I do collect information, though. I often log away in my brain different facts from lecture and my own independent study to use later in my code. I also store tidbits of information about other people and use them later in our interactions. I have seen aspects of my strengths play out while at Turing, and I now recgonize those strengths and capitilize on them when I can.

	2. I came to Turing because I was not happy in the career path I had chosen, but I was still not entirely convinced that I was going to love learning software development. I thought this was a good opportunity for me to become a more employable worker and if I didn't want to do development as a career, I'd work for a couple of years to pay off the tuition and I could try another career. After 4 weeks of lectures, projects, independent study, and being a part of the Turing community, I am certain I want to pursue a career in software development, which is very exciting! I have definitely had my highs and lows at Turing. I have gotten better at recognizing when I am at a low, and taking breaks and providing myself sufficient care to get me back on track. When I have successes at Turing, they spur me forward to learn and grow more.

	3. I don't exactly know what I want my future outside of Turing to be. There many directions software development can take me, so I want to at least experience the industry before I make a decision about what sort of career I want to pursue. My goal after Turing is to get a few years of experience working in the industry, so I can connect with the community and start discovering different career paths. I would also like to see what opportunities the conservation field may have for software developers.

	4. The most difficult part is sharing my future vision. I am young and Turing was and is my introduction into the coding industry. Because of that, I just don't know where I want my career to take me. I see this as an issue future employers may have with me, since they might interpret my indecision as a lack of motivation and drive. I think to improve this aspect of my story, I can start to connect myself more with the tech industry here in Denver. I should meet with mentors to discuss the different career paths available and reach out to people in those areas to find out more.