ana-jauregui · April 15, 2017 20:13
diff --git a/Career Development Prework b/Career Development Prework
 1.
 *Say "I don't know".
  Being able to say "I don't know" is something I find very important whether or not you are learning and new to something or 
  if you are considered a professional. There is always that moment you run into what is a new situation that you may not know
  how to approach for the best solution. I was not always comfortable with saying I don't know, out of fear that maybe I should know.
  I realized over time that I will never have all the answers or know everything in any given subject, nor do I want to. It is best to 
  constantly run into the "I don't know" moment, and learn something new! Once you can be comfortable saying that you don't know, that 
  simple addmission allows the opportunity to learn quicker and probably discover more resorces than you would if you let a fear of 
  imperfection or lack of knowledge get in the way and maybe never truly know. 

 *Act as a leader not a boss.
  This concept is very near and dear to me as I have always been put in a leadership role in every job I have had. It is extremely 
  important to work with your team and know how to play off eachothers strengths. I do believe that while you are in a leadership role you 
  are only as strong as your weakest team member and a good leader should understand that one is more successful when those who you lead 
  are better or stronger than you are. I agree with how simply the article puts it, no matter if you have the official title or not a 
  leader is someone other team members go to for advice and respect for the work they put in themselves. Quite different from the concept 
  of a "boss" who has people who do work for them but do not necessarily have the know-how or truly understand the degree of work it takes
  from each  team member to be successful. I always strive to be a leader rather than a boss, if not a strong member of any team. 
  
 *Move Fast and Break things.
  This is a concept that I really appreciate because it makes learning to code seem like a more attainable goal for myself. However, 
  I do believe that I may struggle to actually put this thought into practice to some extent while I learn to get comfortable in the role
  of coding. I tend to be a perfectionist and sometimes it slows me down in presenting my work until I have something I am really 
  comfortable with because I fear how it may be perceived otherwise while my work may be in progress and needing revisions. I 
  tend to be the kind of person who wants to always give my best and have that be what I share with others. The idea of moving fast and 
  breaking things and truly using those as moments to learn and grow is one that I set as a challange to myself as I move forward to be as 
  successful as I can during my career transition.
  
 2.
 I do strongly believe checklists to be an effective way to organize work that needs to be done in a systematic manner. The challange 
 sometimes can be when it comes to situations that may not necissarily seem so systematic as in healthcare, where there can be so many 
 different approaches to one situation. Even so in such situations checklists can be compliled to have a simpler approach on gathering
 the information necessary. I think that checklists in general help us to think through steps and re-route our thoughts when we 
 may be distracted in the slightest way. As a student learning such complex new ideas that I have little to no familiartiy with, checklists 
 will help me to keep from missing simple steps that could potentially cause a big headache and allow me not have to rely soley on memory. 
 Having a checklist will help me to become a coder who uses a systematic approach. When I make the transition from student to career 
 developer I believe having checklist will continue to help me to stay organized and again avoid simple mistakes that can be overlooked 
 while workingon complex projects. I thnk that a checklist should always be seen as a strong tool used by those who acheive success, 
 rather than a crutch. Checklists lead to consistency.

 3.
 *Strengths-based development seems as though it should be common sense practice but actually very rare in the workplace. I believe it is a 
 practice that works well and bennefits both employees and employers at the same time, keeping employees happy and fulfilled with what they
 are doing and in turn increasing productivity in the workplace. I find it interesting to know of some of the top companies taking this 
 approach to the work environment and clearly these companies must be doing something right. I wonder why more employers don't adopt 
 the strengths-based development model. 

 *I feel that my top strengths are listening, and perseverance. I consider myself to have good communication skills, which is fueled by my
 awareness of peoples differing personalities. I come to understand through listening to others thoughts as well as body language. 
 This makes it easier for me to communicate effectively with a variety of personalities, although I am shy by nature. 
 Perseverance is another strength of mine. Although I find that I am often my own worst enemy when it comes to getting ahead due to fear 
 of failure, I do persevere through my uncertainties and discomfort and thrive when I challange myself to push past those fears to succeed.

 *I hope to be able to become an even better communicator, and more outspoken in a team atmosphere. I hope to be able to push aside
 my fear of failure and open up to accept that I will learn and become a stronger developer while embracing my mistakes.
	1.
	*Say "I don't know".
	Being able to say "I don't know" is something I find very important whether or not you are learning and new to something or
	if you are considered a professional. There is always that moment you run into what is a new situation that you may not know
	how to approach for the best solution. I was not always comfortable with saying I don't know, out of fear that maybe I should know.
	I realized over time that I will never have all the answers or know everything in any given subject, nor do I want to. It is best to
	constantly run into the "I don't know" moment, and learn something new! Once you can be comfortable saying that you don't know, that
	simple addmission allows the opportunity to learn quicker and probably discover more resorces than you would if you let a fear of
	imperfection or lack of knowledge get in the way and maybe never truly know.

	*Act as a leader not a boss.
	This concept is very near and dear to me as I have always been put in a leadership role in every job I have had. It is extremely
	important to work with your team and know how to play off eachothers strengths. I do believe that while you are in a leadership role you
	are only as strong as your weakest team member and a good leader should understand that one is more successful when those who you lead
	are better or stronger than you are. I agree with how simply the article puts it, no matter if you have the official title or not a
	leader is someone other team members go to for advice and respect for the work they put in themselves. Quite different from the concept
	of a "boss" who has people who do work for them but do not necessarily have the know-how or truly understand the degree of work it takes
	from each team member to be successful. I always strive to be a leader rather than a boss, if not a strong member of any team.

	*Move Fast and Break things.
	This is a concept that I really appreciate because it makes learning to code seem like a more attainable goal for myself. However,
	I do believe that I may struggle to actually put this thought into practice to some extent while I learn to get comfortable in the role
	of coding. I tend to be a perfectionist and sometimes it slows me down in presenting my work until I have something I am really
	comfortable with because I fear how it may be perceived otherwise while my work may be in progress and needing revisions. I
	tend to be the kind of person who wants to always give my best and have that be what I share with others. The idea of moving fast and
	breaking things and truly using those as moments to learn and grow is one that I set as a challange to myself as I move forward to be as
	successful as I can during my career transition.

	2.
	I do strongly believe checklists to be an effective way to organize work that needs to be done in a systematic manner. The challange
	sometimes can be when it comes to situations that may not necissarily seem so systematic as in healthcare, where there can be so many
	different approaches to one situation. Even so in such situations checklists can be compliled to have a simpler approach on gathering
	the information necessary. I think that checklists in general help us to think through steps and re-route our thoughts when we
	may be distracted in the slightest way. As a student learning such complex new ideas that I have little to no familiartiy with, checklists
	will help me to keep from missing simple steps that could potentially cause a big headache and allow me not have to rely soley on memory.
	Having a checklist will help me to become a coder who uses a systematic approach. When I make the transition from student to career
	developer I believe having checklist will continue to help me to stay organized and again avoid simple mistakes that can be overlooked
	while workingon complex projects. I thnk that a checklist should always be seen as a strong tool used by those who acheive success,
	rather than a crutch. Checklists lead to consistency.

	3.
	*Strengths-based development seems as though it should be common sense practice but actually very rare in the workplace. I believe it is a
	practice that works well and bennefits both employees and employers at the same time, keeping employees happy and fulfilled with what they
	are doing and in turn increasing productivity in the workplace. I find it interesting to know of some of the top companies taking this
	approach to the work environment and clearly these companies must be doing something right. I wonder why more employers don't adopt
	the strengths-based development model.

	*I feel that my top strengths are listening, and perseverance. I consider myself to have good communication skills, which is fueled by my
	awareness of peoples differing personalities. I come to understand through listening to others thoughts as well as body language.
	This makes it easier for me to communicate effectively with a variety of personalities, although I am shy by nature.
	Perseverance is another strength of mine. Although I find that I am often my own worst enemy when it comes to getting ahead due to fear
	of failure, I do persevere through my uncertainties and discomfort and thrive when I challange myself to push past those fears to succeed.

	*I hope to be able to become an even better communicator, and more outspoken in a team atmosphere. I hope to be able to push aside
	my fear of failure and open up to accept that I will learn and become a stronger developer while embracing my mistakes.
No results found