-
The three behaviors that resonate with me are understanding that code is cheap, be capable of writing bad code and act as a leader. In my own experiences so far I've come to realize that you must be ready to scrap your code and start over. You cannot hang on to improper code just because you invested time writing it. Additionally, while I believe the balance of writing bad code/seeking perfection is something I will struggle with, I'm aware that it will be an important skill when I must meet deadlines in my future career. Finally, acting as a leader is something I value very much. Being a leader means that although people will follow and listen to you, you are not above them and are certainly not above doing grunt work.
-
While I was also initially resistant to using a checklist, I cannot deny their necessity. In my current job when opening and closing the office, I do the same several things everyday and I will still miss things. It is a foolish idea to think that you'll remember everything all the time. Coding is full of so many little details that a checklist could prove essential. I could see if being especially useful when debugging wrong code. Instead of freaking out, it will be best to go through a checklist of common reasons the code is not working.
-
I can see the merits of strength based development because it involves working with what you have instead of trying to change it. While training can improve minor shortcomings, you will ultimately be better at a job that involves utilizing your innate abilities and interests. While I don't have questions about this approach at this moment, I am wondering how a strength based approach plays into actual coding. I am relatively secure in my top strengths of being patient, collaborative and open to trying new things. Throughout my life I have always been able to stay calm and wait when necessary. I hope to utilize my patience to be persistent when faced with a challenging programming problem. As long as I know there is answer, I can keep searching and thinking until I figure it out.
Last active
February 28, 2018 01:09
-
-
Save airum82/49699caf65551afcebb3ab7cc49b6ddc to your computer and use it in GitHub Desktop.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment