Is this the wrong way of thinking? I am the only employee. I'm supposed to do what I'm good at, and that's coding... not talking.
Eventually, if my product is good enough, someone has to notice. Right...?
Is this the wrong way of thinking? I am the only employee. I'm supposed to do what I'm good at, and that's coding... not talking.
Eventually, if my product is good enough, someone has to notice. Right...?
As an engineer, you might be tempted to call those people "bullshitters", because they talk more than they create. They're not - they have different strengths than you do, that is all. And when you need somebody to talk, you want those people.
And so, knowing them is a good plan. As is, in general, building a network of people you can contact for advice on things you're not good at. This is not about going there and talking. This is about going there and finding people who can complement your strengths. This is about getting feedback on your product. This is about hearing new ideas.
All of that will benefit your product.
If it's not solely for you, and you do really want to build a good product, then you have to listen to what people say about it. And you can't just close your ears when they stop talking about your product and about themselves and their own problems; to be a good listener you have to listen to all of it.
Retreating into what you're good at is just that: retreating. To make progress in any area you have to get past obstacles, including the ones you create for yourself. In the end, you will never be successful without communicating. And communicating goes both ways.