While moving my way up various positions within two different industries, I always felt my excitement fade within a few months of being promoted. I often felt bored and unchallenged after figuring out the best way of doing things in the position I was in. Though I was promoted often, I felt like there was more I could do to challenge myself and get better. Observing people around me made me realize that comfortability often leads to stagnation. This sent me on of a quest for knowledge. I knew that I wanted to learn something challenging, and something that kept me on my toes. Programming is exactly that for me. I am always being challenged and there is just so much out there that I don't know. Knowing that I will always be challenged excites me. There will never be a time when I know everything about how to do things in this industry.

I started programming on free sites like Codecademy and The Oden Project but I quickly realized that I could learn faster a

The assignments listed here should take you approximately 25 total minutes.

To start this assignment, click the button in the upper right-hand corner that says Fork. This is now your copy of the document. Click the Edit button when you're ready to start adding your answers. To save your work, click the green button in the bottom right-hand corner. You can always come back and re-edit your gist.

You can reference the files/directories portion of the lesson here.

The readings and responses listed here should take you approximately 20 minutes total.

To start this assignment:

1. Click the button in the upper right-hand corner that says Fork. This is now your copy of this document.
2. Click the Edit button when you're ready to start adding your answers.
3. To save your work, click the green button in the bottom right-hand corner. You can always come back and re-edit your gist.

The readings and responses listed here should take you approximately 1.5 total hours.

To start this assignment, click the button in the upper right-hand corner that says Fork. This is now your copy of this document. Click the Edit button when you're ready to start adding your answers. To save your work, click the green button in the bottom right-hand corner. You can always come back and re-edit your gist.

• Your key take-aways OR how you're going to implement specific points (minimum 3):
• When she talks about all the things she did before coding, this gives me hope. I also am not a young person getting into coding, I've had several careers that have all lead to this.

The assignments listed here should take you approximately 2 hours.

To start this assignment, click the button in the upper right-hand corner that says Fork. This is now your copy of the document. Click the Edit button when you're ready to start adding your answers. To save your work, click the green button in the bottom right-hand corner. You can always come back and re-edit your gist.

Documentation of a langauge, framework, or tool is the information that describes its functionality. For this part of the practice tasks, you're going to practice digging into documentation and other reference material.

1. Empathy has always been important to me. I've talked about it many times as a manager about how you have to have eachothers backs which I think starts with empathy. It's helped me in my career, being able to feel what others feel is very beneficial when trying to be successful as a team. My wife and I talk about how important empathy is in our relationship. It seems that empathising is very beneficial when working with others on anything really.

2. Empathy must help when building software by opening you up to cunstructed critisism. When you know someones intentions are to help, it's a lot easier hearing them give you direct advice over your code. Software development in general seems like a very TEAM oriented career. Not many people can build something that's great on their own. There is probably lots of reasons empathy can help with software development, I look forward to learning some.

3. It is important for teamwork because it allows you to know why others are doing cer

1. Use Google Aggressively. Over the last year I have tried to teach myself full stack development. It's been a bumpy road and one that is full of google searches. I imagine the amount of 'googling' I will be doing will grow quite a bit. I've found that with most of my more intricate questions I always end up on stack overflow. I can see how in the near future I will be using a lot of google which I am thankfullly familiar with.

4. Acknowledge that most major decisions don’t matter that much. This one resonates with me becuase it was kind of shocking to read. I am the type of person that really likes to take my time with big decisions. This portion of the article tells me that I can't obsess. I have to learn to make a decision on some things and move on. I like the idea of becoming a zen-like programmer.

10. Know the difference between a premature optimization and a show-stopping optimization that NEEDS to happen. This one also resonates with me due to my percieved challeng