Maxscores/Stackhouse1710-bCareerDevelopment.txt

## Stackhouse1710-bCareerDevelopment.txt
8, 11, 16, 29
1) The three behaviors I felt resonate the most in the article "29 Behaviors That Will Make You an Unstoppable Programmer" were all
based around the theme of Ego. Behavior #8 tells us to become comfortable with saying "I Don't Konw". To me, this is truely fundamental
when it comes to work and life, because there are too many different situations to truely know the answer to everything before trying a
solution. Being ok with not knowning the solution tends to gives one the freedom to make mistakes and use them for learning opportunities,
which is the idea behind Behavior #11. Along the same lines is behavior #16, this is being able to take outside criticism against one's
work. I believe it is crucial to be able to take critism to improve and become the best version of ourselves. In sports, the best players
tend to not only be extremely talented, but constantly learning and improving their game through listening to criticism.

2) I love the idea of using checklists as a student and programmer. I've been using checklists for years when managing my chores around
the house, at work and when planning for a big trip. I find that sitting down and writing out a checklist of all of the things I need to
accomplish keeps me on task and allows me to get everything done. Many times I will become deeply focused on a task, such as cleaning the
house and I end up performing additional tasks that were not originally on the list, but needed to be taken care up anyway. Afterwards I
will forget what the next task was that I needed to do. Without a list, important tasks can easily be overlooked and forgotten.

3)To me, strengths-based development feels like a natural step in the progression of our individual based society. My biggest question is
how individuals actualy adhere to the principles of the development. In most of the environments that I've worked the management team
push 'personal development' onto the employees in a yearly review, but never really seem to care about it outside of the review process.
I feel that some of my strongest strengths are in teamwork, big picture thinking and seeing related threads. I've seen these through my
years of playing sports (pass first mentality), seeing what is important at work, and learning new things by relating them to things
that I already know. I hope to keep building on these ideas when applied to software development, because it seems to me the area where
forward thinking frameworks such as strengths-based development are being applied.
	8, 11, 16, 29
	1) The three behaviors I felt resonate the most in the article "29 Behaviors That Will Make You an Unstoppable Programmer" were all
	based around the theme of Ego. Behavior #8 tells us to become comfortable with saying "I Don't Konw". To me, this is truely fundamental
	when it comes to work and life, because there are too many different situations to truely know the answer to everything before trying a
	solution. Being ok with not knowning the solution tends to gives one the freedom to make mistakes and use them for learning opportunities,
	which is the idea behind Behavior #11. Along the same lines is behavior #16, this is being able to take outside criticism against one's
	work. I believe it is crucial to be able to take critism to improve and become the best version of ourselves. In sports, the best players
	tend to not only be extremely talented, but constantly learning and improving their game through listening to criticism.

	2) I love the idea of using checklists as a student and programmer. I've been using checklists for years when managing my chores around
	the house, at work and when planning for a big trip. I find that sitting down and writing out a checklist of all of the things I need to
	accomplish keeps me on task and allows me to get everything done. Many times I will become deeply focused on a task, such as cleaning the
	house and I end up performing additional tasks that were not originally on the list, but needed to be taken care up anyway. Afterwards I
	will forget what the next task was that I needed to do. Without a list, important tasks can easily be overlooked and forgotten.

	3)To me, strengths-based development feels like a natural step in the progression of our individual based society. My biggest question is
	how individuals actualy adhere to the principles of the development. In most of the environments that I've worked the management team
	push 'personal development' onto the employees in a yearly review, but never really seem to care about it outside of the review process.
	I feel that some of my strongest strengths are in teamwork, big picture thinking and seeing related threads. I've seen these through my
	years of playing sports (pass first mentality), seeing what is important at work, and learning new things by relating them to things
	that I already know. I hope to keep building on these ideas when applied to software development, because it seems to me the area where
	forward thinking frameworks such as strengths-based development are being applied.