This is very relatable for me. I've learned that not asking for help or acknowledging that you do not understand is a way to be unsuccessful. In my life, I have felt before like I knew more than I did and sometimes in school I was too proud to ask the teacher or fellow students for help. Confidence is good but arrogance can lead to failure. This is something I learned the hard way in college.
This is always challenging and something many people struggle with. I especially find this difficult when working on a team out of fear of being ridiculed by my teammates. It emphasizes again why empathy and understanding are so important while working on a team. People need to feel comfortable taking responsibility for their mistakes.
It is easy for me to get so wrapped up in something I forget about other aspects of a project. Balance is the key to success in many areas of life, and coding is no exception. While organizations have different people working on those parts of the business, it is still important to keep them in mind as the programmer. While working for a community service learning center at my university, I had many more tasks than just my primary role. I helped my supervisor organize paperwork, helped clean up the work area, and did little tasks for others. That work was important as well as my primary role as a van driver.
I personally like the idea of the checklist. I see no harm in it, it is safe, and it makes the customers (patients) more comfortable. Keeping the checklist fast so it is not tedious, just a reminder does more help than harm. If you begin using the checklist as a student, I believe you will be much more likely to utilizie it in the workplace. It could end up helping you work more efficiently and your work being completed more thourougly.
What is your impression of strengths-based development? What questions do you have about this kind of development? It is a very different approach to hiring than the traditional interview process. It seems like somewhat of a role reversale: you do not select the candidate best fit for the job, you make a job best fit for the candidate. I've taken the MBTI test many times and I find it fascinating to study that kind of psychology related to personality. I think the revolution of creating new ways to test peoples personality to determine if they are good for a job, or finding peoples strengths and applying them to jobs is very interesting work and creates jobs in itself. Playing on people's strengths and seeing them as a positive asset will help them contribute more the workforce. No one wants to think the need to be "fixed", the want to be appreciatd for who they are. People who believe their skills are valuable will be more motivated to contribute to the work. I wonder, will the MBTI test be completely disregarded eventually? Will this new approach be adopted by more companies than facebook? What do you feel are your top strengths? How do you know? I am easy to get along with, very open minded, and hardworking. I do not give up on anything. If there is a negative trait associating with me, it would be I am stubborn because when I start working on something I always give it my all. I almost don't know when it's time to quit, because I never want to quit. How do you hope to develop your strengths for your new career in software development? I hope to work with open minded people who share my views of the world. I think I will find a niche that I enjoy in software development and make a difference in whichever area peaks my interest.