## 29 Behaviors Article Reflection
### Pick out 3 behaviors that resonate with you in the list and describe why they resonate with you in a reflection (4-6 sentences).
The first behavior that resonated with me was understanding that “code is cheap” because I have been guilty of falling for the sunk-cost fallacy before while writing short programs.  In particular, I spent a couple of days attempting to write a program for a specific dark room timer and was very reluctant to ditch my code in favor of another (better, faster)
 approach because I had put so much time into it already.

The second behavior that stood out to me was to always analyze error messages. While writing the number-guessing game for the pre work, I got error messages frequently and eventually learned how to use them to help me fix problems in the code.

The third behavior that I found helpful to read about was how to absorb massive criticism with ease.  I particularly liked the advice on how to respond to criticism that you disagree with - by giving the person offering feedback credit for their thoughts while also calmly defending your position.
_____
## Checklist Article Reflection
### 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.
One benefit of using checklists is that they can help you keep track of seemingly trivial tasks so that you can focus on more complex tasks instead.  Checklists also free up short-term memory space and serve as a safety-net so you are less likely to forget to complete necessary tasks.  Checklists could help me keep track of larger assignments and protocols as a student. Also, since Turing requires me to learn at such a fast pace, checklists could externalize some information for me and reduce mental strain to a degree.  As a full-time developer, checklists could help me keep track off deadlines, new protocols, and tasks such as responding to emails in a timely manner.
_____
## Strengths-Based Development Reflection
### What is your impression of strengths-based development? What questions do you have about this kind of development?
I think that strengths-based development is a good idea (in theory at least) because it enables people to focus on maximizing their strengths and finding a position where those strengths are most effectively utilized.  However, I think that strengths-based development is only feasible in some work environments and not others.  For instance, when working as a member of a large team, you may be able to “specialize” in your strengths more easily than you could when working on a small team where you have no option but to be well-rounded in order to deliver a product or service.  Some questions I have:  1) How do a growth mindset and strengths-based development align?  2) Approximately what percent of tech companies currently hire and/or develop their employees with the strengths-based approach?

### What do you feel are your top strengths? How do you know?
I think that my top strengths are visual reasoning, organization and adaptability.  I naturally think through complex problems by visualizing how the interconnected pieces work together, and I understand concepts best when delivered visually (not orally).  I also like to be highly organized and have noticed that I seem to be more organized than the majority of my colleagues.  Lastly, I have been told that one of my strengths is that I am flexible and adapt quickly to changing situations - I easily “roll with the punches”.

### How do you hope to develop your strengths for your new career in software development?
I hope to master utilizing tools that are specific to the software industry in order to build upon my strength in organization.  I also hope to apply my organizational skills to help lead teams in the future and best assign/prioritize the tasks of the team. As I learn programming, I also hope to learn how to use my strength of visual reasoning to communicate clearly and effectively with team members through diagrams and pictures.  Finally, I hope to continue to learn programming languages and concepts far beyond Ruby so that I can maximize my strength of adaptability for my company/team.