kmarler2 · January 13, 2018 01:53
diff --git a/Keeliana.Marler_ProfessionalDevelopment b/Keeliana.Marler_ProfessionalDevelopment
 1. http://blog.thefirehoseproject.com/posts/29-behaviors-will-make-unstoppable-programmer/

 I think that the three points that resonated the most with me were "Use google very aggressively", "Take responsibility for their mistakes",
 and "Learn under pressure. I sometimes will jump into things, even if I'm not sure what I'm doing. Using google and researching for several
 minutes could save me lots of time and energy! I also think its really important for me to take responsibility for mistakes, especially when 
 working on team projects. Admitting I am wrong will not only save resources, but also serve as a valuable learning opportunity. Learning 
 under pressure is also very important to me, especially when working in a tech based career. Our tools and technology is changing constantly, 
 so its very important to be able to learn new programs and ideas in high stress or less than perfect instances.

 2. https://www.npr.org/templates/story/story.php?storyId=122226184
 I learned a lot from this article! Even though surgeons may have ten or more years of training, its still possible to make basic, easily 
 avoided mistakes. I think for this reason, its very important to remember the basics. Even tiny, basic mistakes can cause the entire program 
 to not work, and not making these mistakes in the first place is much more effecient. 

 3. I think strength based development is a great idea. In a team situation, you don't look at people's weaknesses, but rather assess their
 individual strengths. I think we should build up each other's strengths and also fill in other people's "gaps" with our own unique set of 
 skills. From past experience working in teams, I think my best strengths are that I can get along well with just about anyone, initiative, 
 and the ability to plan ahead. I think that the main thing I need to work on is follow through, and I hope to improve that greatly by
 gaining the accountability that working with others provides.
	1. http://blog.thefirehoseproject.com/posts/29-behaviors-will-make-unstoppable-programmer/

	I think that the three points that resonated the most with me were "Use google very aggressively", "Take responsibility for their mistakes",
	and "Learn under pressure. I sometimes will jump into things, even if I'm not sure what I'm doing. Using google and researching for several
	minutes could save me lots of time and energy! I also think its really important for me to take responsibility for mistakes, especially when
	working on team projects. Admitting I am wrong will not only save resources, but also serve as a valuable learning opportunity. Learning
	under pressure is also very important to me, especially when working in a tech based career. Our tools and technology is changing constantly,
	so its very important to be able to learn new programs and ideas in high stress or less than perfect instances.

	2. https://www.npr.org/templates/story/story.php?storyId=122226184
	I learned a lot from this article! Even though surgeons may have ten or more years of training, its still possible to make basic, easily
	avoided mistakes. I think for this reason, its very important to remember the basics. Even tiny, basic mistakes can cause the entire program
	to not work, and not making these mistakes in the first place is much more effecient.

	3. I think strength based development is a great idea. In a team situation, you don't look at people's weaknesses, but rather assess their
	individual strengths. I think we should build up each other's strengths and also fill in other people's "gaps" with our own unique set of
	skills. From past experience working in teams, I think my best strengths are that I can get along well with just about anyone, initiative,
	and the ability to plan ahead. I think that the main thing I need to work on is follow through, and I hope to improve that greatly by
	gaining the accountability that working with others provides.