I started writing software in 1984. Over the years I worked with many languages, technologies, and tools. I have been in leadership positions since the early 2000s, and in executive roles since 2014.
I think the big question is: do you believe this is a problem that you need to somehow resolve? Or do you believe that it is not a problem at all?
If you believe it is a problem that you want to solve, there are many paths for you to take to resolve it.
If you believe it is NOT a problem and/or you have no interest in "changing it," then I think you can build your career as a developer around it, recognizing that it might get in your way. When it does, it helps to have defined strategies to follow.
I really don't know what to think. I'd prefer for it not to be a problem. But it's a problem, when for example, sucking at marketing makes it hard to find someone who is good at marketing.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I think the big question is: do you believe this is a problem that you need to somehow resolve? Or do you believe that it is not a problem at all?
If you believe it is a problem that you want to solve, there are many paths for you to take to resolve it.
If you believe it is NOT a problem and/or you have no interest in "changing it," then I think you can build your career as a developer around it, recognizing that it might get in your way. When it does, it helps to have defined strategies to follow.
I really don't know what to think. I'd prefer for it not to be a problem. But it's a problem, when for example, sucking at marketing makes it hard to find someone who is good at marketing.