Professional_Development_pre-work.md

1. Behavior 1: "Use Google very aggressively" -> The strategy of the 10 tab is a simple strategy for performing research without getting too far down an incorrect rabbit hole. Behavior 2: "Understand that 'code is cheap.' " -> Feeling confident in letting go of code and not falling prey to the sunk cost fallacy can save time and energy. Behavior 3: "Know the difference between a premature optimization and a show-stopping optimization that NEEDS to happen" -> This reminds me of an 80/20 analysis and deciding where to strategically place time and resources that will have the most significant impact on the business.

2. The benefits of a checklist including being developing systems to approach similar problem sets. This promotes attention to detail and a higher quality of product delivery. This could be beneficial, as a student, for creating a checklist for troubleshooting errors in code. As a full-time developer, this could be useful for coding faster and with a higher degree of accuracy, especially in high pressure circumstances (like a website crashing).

3. My impression of strength-based development is that it is important to cultivate the areas we are historically strong at. Learning to display and market these skills could be a very important aspect of marketing myself while job hunting. One of my top strengths includes creative problem solving. I have come to this conclusion, as I often synthesize diverse solutions in circumstances others are not able to. I also have strong leadership skills, as I have studied leadership training material, I integrate what I learn, and I receive positive feedback about my leadership abilities. I hope to enhance these skills in my software development career by stepping up to opportunities and continuing to seek out mentors and further learning material.