#6 That code is cheap To know when it is time to scrap code because writing in a different way would be optimal. That is, if I spent one week on code that would require me to constantly perform maintenance of it when the number of users reach a certain threshold rather than rewriting the code to selfupdate at these threshold, would not be optimal. I have a small codebase now that performs login validation, there are many side effects in my code and instead of fixing each case as hey happen, it would be a better use of my time to correctly code it with no unwanted side effects built in.
#8 Say "I Don't Know." Knowing when it is ok to ask for help is really important. I used to be in the group that refused to ask for help and would "figure it out" on my own. While this approach does work, I found there are major drawbacks to it. Namely that often the solutions one finds alone often times have issues themselves and two by saying you don't know you can enlist the help of a person more familiar to your problem that may give a more tailored solution.
#16 Absorb massive criticism with ease Constructive criticism is good. Being able to accept the critical analysis of another is paramount in becoming a better person. Also, being able to justify your approach in an approachable manner is also key, try not being defensive.
Checklists are great tools that enable one to have a central repository for tracking. A nice side effect is that you have a document that you can glance at quickly to help with your time management. A trick I like to use is to list tasks and then just give an honest guess at how long the tasks is expected to take and then reflect on how honest I was(Since time is limited). This helps me in the future making checklists that are realistic.
-
Sounds very promising. That is, there is a great argument there that constantly focusing on improving weakness overlooks being able to fully make us and develop further, strengths. These strengths could bring more value to the company than soley, or mainly focusing on weaknesses. I would also say there is a huge caveat, some weakness are catastrophic in nature and must be improved such as poor interpersonal skills. This absolutely should not be ignored to improve strengths.
-
I feel my strengths are that I am open to criticism, have experience in leadership roles so I can apply that knowledge when working for leaders, and I have no qualms in admitting I need assistance. I am a huge advocate for fairness, equal opportunity, asking for clarification. My last job gave yearly reviews and it is my source document.
-
I hope to develop my strengths further by applying them while being part of a team. If there are issues with the software and it is not clear where the issue stemmed from I would quickly step in and take ownership for it and lead on finding a fix if appropriate. This allows us to quickly move on to other matters and not be stuck in a blame game which can ruin cohesion.