As a programmer should you know it all up to the go to market strategy or you should definitely depend on a professional for this aspect of development
For further actions, you may consider blocking this person and/or reporting abuse
As a programmer should you know it all up to the go to market strategy or you should definitely depend on a professional for this aspect of development
For further actions, you may consider blocking this person and/or reporting abuse
Louis Bertson -
Vaishakh Anil -
Danish -
yukaty -
Top comments (1)
That's a good question and I don't know the answer, but I think it's a bit of a balance.
It's important to know the direction of a product and the reason the company needs the feature you are coding. If you know 'why?' then you can begin to think critically. When you can think critically you can give feedback to product and design people. Everyone's perspective is valuable in a company, and as a programmer you can give insight into the time it takes to implement something, or the kind of crazy things that are possible in your application that only a developer might think of.
On the other side of the coin, focusing on what will benefit you and the company is important. Any given company has tons of information and strategy floating around. You should decide what area of the company is important to you and what you think you can make a difference in. Then you will know what you should learn.
The most important thing is to just try! See what works and what doesn't. Talk to designers and product people and salespeople and get new perspectives. You never know when it might all come together.