Pick out 3 behaviors that resonate with you in the list and describe why they resonate with you in a reflection (4-6 sentences).
"Acknowledge that most major decisions don’t matter that much" is a behavior I need to keep in mind because I have strong opinions and can tend to get caught up in those decisions. I want to learn to value the big picture and not get caught up in the debates about the smaller details that make up the big picture (e.g. the spaces vs. tab debate).
I also want to learn to value the idea that "code is cheap." It can be frustrating to come to the realization that you just spent hours working on a solution that may need to be scrapped in lieu of a better solution. However, if in the long-run you produce a better product and ultimately less time, that initial scrapped work was part of the path that led to the end-results you wanted.
Finally, the 2 behaviors related to learning vim definitely resonated with me. When I first learned about vim, my hyper-efficient mind was fascinated and I resolved that I would become a power-user of vim so that I could be an ultra-efficient developer.
After reading, consider the idea of checklists. Write a reflection (4-6 sentences) on the benefits of a checklist and how an organizational system such as a checklist might help you first as a student and later as a full-time developer.
The heart of the checklist seems to be humility - one must have humility to acknowledge that a checklist can be a useful tool no matter how much experience you have. I see this as a valuable tool for anyone, no matter how many years of experience you have. Anyone can forget something or make a minor mistake and implementing a checklist may seem redundant or tedious but can greatly improve your work quality and teamwork.
As a student, this will help me learn and understand the basics of programming. Additionally, the humility that comes along with implementing the checklist will keep me in learning-mode. As a full-time developer, who will no doubt have lots of other responsibilities on my mind, checklists will ensure that I am not forgetting the basics. It will also help the cause of the overall team in that I'll avoid small mistakes that could have larger implications for the entire team.
Answer the following questions in a reflection (4-6 sentences): What is your impression of strengths-based development? What questions do you have about this kind of development? What do you feel are your top strengths? How do you know? How do you hope to develop your strengths for your new career in software development?
I like the idea of using strengths-based development and I think it's good that it's paired with guidance on managing your weaknesses, too. I think the tendancy for some when reading about Strength-based development is to ignore weaknesses, but that is clearly not a healthy approach.
I've taken StrengthsFinder in the past and know that I spike in the Analytical and Strategic areas. Even without the assessment, these are two areas that I would identify as strengths based on my problem-solving skills and ultra-rational mindset.
Software development is the problem-solver's dream, but I hope to develop these strengths not only in the nitty gritty details of writing lines of code to implement individual features but also in problem-solving on a larger scale in the development of a full product.