- Take responsibility for your mistakes
- Dive into large open source projects to bring your features to life
- Learn under pressure
- Know when it’s time to give back
The above behaviors resonate with me the most for the following reasons. Taking responsibility for your mistakes may be a difficult habit to develop. However, once you break past the ego and realize owning your mistake is the best way to grow and become a better you. Also, as a developer trying to put the fault on other developers or coworkers only creates a stagnant environment for you and the team. I also enjoy (yes, enjoy) research and diving deeper in to a project or anything really. One of the most enjoyable aspects to creating, for me, is the brainstorming aspect. So I will most likely be that developer or goes in to large open source projects to bring websites and features to life. I also do best when learning and working under pressure. I focus in on the task/project and forget all disctractions. In most high-pressure situations, I tend to shine the most, which is one of the reasons I felt confident I would transtion well in to a developor career. Lastly, I wanted to add an extra behavior because I think it's so important. Know when it's time to give back. I have been so grateful for all the support from the developers in my life. (shout out to Turing Alum, Alan Smith) I will be supporting and encouraging just as others have done for me when the time comes.
Without checklists, erroneous actions are made and important information is forgotten. Therefore, I believe organization such as checklists as a Turing student and later as a full-time developer are vital to success. With organization, there tends to be increased efficiency and less assumptions made. I think one of the best qualities of organizational skills is keeping yourself in check and knowing when and where to correct errors. All in all, we make human errors so building organizational skills would help immensely especially in a developer career.
- What is your impression of strengths-based development? What questions do you have about this kind of development?
I am somewhat familiar with strength-based development from years back in college, and look forward to using it to better align my career in the present. The vision and goals in strength-based development align with my own. Meaning I agree with the view of encouraging the strengths in an individual while also remembering to keep on top of weaknesses. Working through weaknesses nurtures perserverence and self-awareness skills.
-
What do you feel are your top strengths? How do you know?
- Empathy
- Adaptibility
- Problem-solver
- Perserverence I believe the above are my top strengths, which I have become more aware of over the years with the help of job and peer reviews, family and friend communication, self-development, and research in personality traits. I have been told and am aware I jump to help a teammate because of my empathy skills. I also feel I am able to adapt to a number of situations and personalities making it easier to work through a projects and issues/errors. My problem-solving and perserverence skills tend to work in tandem with my other strengths making sure tasks are completed in full and well.
-
How do you hope to develop your strengths for your new career in software development?
I hope to develop my strengths in my softare development career by quickly adapting to a problem-solving scenario. As we know, as a developer there is constantly a puzzle to be solved while staying in-tune with the end goal of a project. This is where I believe my empathy skills will develop. If all teammate's thoughts and ideas are listened to, a project will go smoother. Overall, I believe my skills will organically develop as my career advances while I also learn of new skills in a new career path.