Skip to content

Instantly share code, notes, and snippets.

@andrew-t-james
Created February 4, 2018 21:37
Show Gist options
  • Save andrew-t-james/71c2b6c74fe16173f3c05eadc91a0247 to your computer and use it in GitHub Desktop.
Save andrew-t-james/71c2b6c74fe16173f3c05eadc91a0247 to your computer and use it in GitHub Desktop.

Behaviors

Approximate reading time: 20 minutes Pick out 3 behaviors that resonate with you in the list and describe why they resonate with you in a reflection (4-6 sentences).

The following three behaviors resonate with.

Maintain an obnoxious amount of stick-to-itiveness.
Understand that “code is cheap.”
Always analyze the clues found in error messages

I have found having a stick-to-itiveness has proved a valuable asset during my time as a collegiate athlete, a solider, and now an aspiring developer. Sticking through when times get tough can be what separates you from success and failures. Not to say that you will not fail along the way, that is where analyzing clues found in error messages comes in. With each failure/error you can find the answers you seek moving closer and closer to your ultimate goals. Understanding Code-is-Cheap is something I guess I figured out as I started my journey to becoming a developer. I would write code and feel as if no one should touch it or it would break. Now I write code to get something working, then go back and refactor it to be more efficient.

Organization

Write a reflection (4-6 sentences) on the benefits of a checklist and how an organizational system such as a checklist might help you first as a student and later as a full-time developer.

I think checklists can help keep you on track. When sitting down to develope a new project the amount of work that needs to happen can feel daunting. I have actually looked a project and felt overwhelmed from not knowing where to start. I found breaking things down in to smaller more achievable goals(checklist items) helled me find my way through those feelings of not knowing where to start. Incorporating a check list system would benefit me as a full-time developer by helping me manage the tasks I need to complete.

Strengths

What is your impression of strengths-based development? What questions do you have about this kind of development?

After completing the reading I wish I had more opportunities in other careers to have been evaluated this way. I feel like matching people based on their strengths seems like such a natural step in creating a great work environment where employee's can be successful. Doing work I am not going to struggle at sounds because I don't match the work sounds like a recipe for disaster.

What do you feel are your top strengths? How do you know?

I feel one of my top strengths is perseverance. I know this from my time as a collegiate athlete who didn't compete to ending my career as an olympic trial level athlete, and again in the Military while serving in the Army. I found my self in situations that required an extreme amount of perseverance and seemingly came out successful in meeting my goals or goals I was volun-told to meet.

How do you hope to develop your strengths for your new career in software development?

I am not sure how I will devolved my strengths as developer as of yet. I know from my time learning to date perseverance and the ability to research without loosing my patience has proved a solid answer to solving problems when they arise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment