Activity 1

Pick out 3 behaviors that resonate with you in the list and describe why they resonate with you in a reflection (4-6 sentences).

• Use Google very aggressively
  This idea resonates with me because it tells me that, fundamentally, programmers are not expected to perfectly memorize everything. It is an admission that we just cannot remember everything, and are allowed and encouraged to depend on resources when we need them. It is okay to reserve our brainpower for deeper stretegic thinking and project planning at the expense of knowing all of a language or application in fine detail. I expect that the fine details will eventually begin to stick, through sheer repetition, but appreciate the upfront declaration that there is no shame in using good resources.
• Always analyze the clues found in error messages
  This behavior resonates not because I already understand error messages, but because of the sentiment that error messages aren't our enemy or a reflection on the programmer as a human being. As I read, I was brainstorming what else the error message could be called to impart less 'failure'. Perhaps something similar to 'Malfunction Information'? I don't ever hear people speaking about their own malfunctions, because that word lends itself to systems or processes, so maybe this title would make it less personal. It is also important to just be mindful of your own feelings of personal failure, and separate the two worlds intentionally!
• Become a power-user of your development tools I like this idea because we are about to learn a ton of new tools and skills, and it's important to recognize how easy it would be to get distracted along the way. There will always be new, shiny, fun pieces of software, but its important to start with the basics and learn them very well. Then we'll have a better sense of what the new thing might offer, and be able to apply the proper critical thinking to judge if the time investment is actually worth the benefit!

Activity 2

I'm a firm believer in the use of checklists! I think people are wise to thoughtfully limit the amount of information we store only in memory. If we use intelligent lists we keep brain power available for more analytical tasks, as opposed to sheer memorization, and that's a good thing. The only flaw occurs when people creates lists and do not have the willpower to stick with them -- then they've wasted time making the list, and still rely on their brain to accomplish everything.

Activity 3

• Step 1
• Step 2
• Step 3

1. I believe my greatest strength is that I'm very introspective and know myself quite well. That doesn't mean that I'm perfect, happier than others or done developing, just that I'm aware of myself. I deeply value critical thinking and lifelong learning, so self-awareness feels like a solid foundation to grow from.
2. I generally work best alone, with a long and difficult problem to solve. I enjoy researching solutions and weighing options then taking strong action when I've come to my conclusion. Although I like working with others, its rare that I can let go and give up control to those that I don't trust or sense equal commitment from.
3. My greatest area for improvement is my ability to trust in others. Because of lessons from past careers, this does not come naturally anymore. I'm aware of that and happy to be moving into a field where this will be less drastic.
4. I hope to maximize my strengths by learning a lot, and slowly moving into project management roles. I'm excited to sit back and learn for a while. I'm also excited to work on new projects, work with a variety of people, and just kickstart some big changes in my professional life. I really want to do work that makes me proud (while supporting my life).

• Optional Reading