<h1>Professional Development</h1>
<h2>29 Behaviors That Will Make You An Unstoppable Programmer<h2>
<h3>Acknowledge that most major decisions don’t matter that much.</h3>
<p>It's more important to focus on the end goal than how you get there. In the end all the situations and decisions that you thought were extremely important will be immediately forgotten about.<p>
  <h3>Always use the right tool for the job.</h3>
  <p>forget about the tool that you are most comfortable with use what best fits that task at hand. Step out of your comfort zone and learn something new</p>
  <h3>Go play foosball, don't count hours, skip a lot of meetings write bad code fast and break things</h3>
  <p>Realize that deep thinking will get you there faster. You can only engage your brain this way for so many hours. Invest in yourself with healthy breaks and distractions. skip meetings in the name of more deep thinking and coding. Don't hesitate to throw out a weeks worth of code that sent you down the wrong rabbit hole and start over.</p>
  <h2>Atul Gawande: "Checklists"</h2>
  <h3>Benefits of a Checklist and Having an Organizational System</h3>
  <p>No matter how much knowledge you have a checklist will always make productivity more reliable and more efficient, you are less likely to miss something that could kill the project at hand. A checklist also makes team work more effective so as everyone communicates on the same level based on the checklist. The biggest example that I can relate to from my childhood is in the world aviation. When I was a young boy my grandfather was a pilot and no matter how many times you have flown you have a checklist that you go through before you hit the runway to take off.</p>
  <h2>Strengths-based Development</h2>
  <p>in Jim Collins "Good to Great: Why Some Companies Make the leap and Others Don't", he touches on this subject in many different ways. In short and can build a good company through fear and force based tactics, where jobs are sync or swim, but if you truly want to build a great long-lasting company then you have to employ and strengths based environment</p>
  <p>I feel that my strengths are in creativity, thinking outside the box, problem solving, and focusing on the solution more so than that problem or task at hand. I know this because I pay attention to what's going on, I fix things with ease, I don't focus on problems rather solutions, I see things others don't see, if I see something I dont know about I push forward to figure it out when others my just say "I don't know therefore I can not do". Another big reason that I know is because I do not function well in the fear and force based, sink or swim job environment, where creativity is drowned and thinking is frowned upon.</p>
  <p>I hope to develope my strengths as a programmer by welcoming constructive criticism, not being afraid to scrap and start over, speaking up without fear, and excepting failure as opportunties to achieve greater goals.</p>