"For example, I know that one of my weaknesses is trying many things myself without asking for help." -- this can slow you down in the short term, but on the other hand it's a sign of a learning mindset, where you try to figure things out yourself rather than getting bailed out whenever things get difficult. I prefer to err on the side of trying to solve things with minimal assistance for that reason, although of course it depends on the situation.
Thank you @destynova
for your kind words! I think you are right, but there is one point I want to emphasize. As you said, the learning mindset is critical for developers, and you should always be in this mindset. But, in "real life" (businesses), you should be careful with it. As I wrote in the "Importance of critical thinking with the right mindset" section - you need to see what the mindset you are in and how it impacts your work. So I still think it is a weakness - not for myself as you said, rather for the company I work for. I genuinely believe for maximizing the "right mindset," you should recognize your weaknesses.
Fair point! But I think it's important to step back sometimes and be careful to avoid too much focus on visible short-term gains for the company, since it can result in missing the bigger picture for long-term opportunities and ideas.
I worked in a small startup once, directly interacting with a CTO who constantly said things like "we need some quick wins". Needless to say, I felt immediately under pressure and stopped thinking about long-term possibilities or learning. Within about 3 months of being hired, I decided it was time to leave before things got worse. At that point I realised why people hired before me never seemed to stick around either :D
"For example, I know that one of my weaknesses is trying many things myself without asking for help." -- this can slow you down in the short term, but on the other hand it's a sign of a learning mindset, where you try to figure things out yourself rather than getting bailed out whenever things get difficult. I prefer to err on the side of trying to solve things with minimal assistance for that reason, although of course it depends on the situation.
Thank you @destynova for your kind words! I think you are right, but there is one point I want to emphasize. As you said, the learning mindset is critical for developers, and you should always be in this mindset. But, in "real life" (businesses), you should be careful with it. As I wrote in the "Importance of critical thinking with the right mindset" section - you need to see what the mindset you are in and how it impacts your work. So I still think it is a weakness - not for myself as you said, rather for the company I work for. I genuinely believe for maximizing the "right mindset," you should recognize your weaknesses.
Fair point! But I think it's important to step back sometimes and be careful to avoid too much focus on visible short-term gains for the company, since it can result in missing the bigger picture for long-term opportunities and ideas.
I worked in a small startup once, directly interacting with a CTO who constantly said things like "we need some quick wins". Needless to say, I felt immediately under pressure and stopped thinking about long-term possibilities or learning. Within about 3 months of being hired, I decided it was time to leave before things got worse. At that point I realised why people hired before me never seemed to stick around either :D
Good point I didn't think about it, seems your decision was correct (in my point of view), I wish you good luck :)