4 ms·

I think it's just the insecurities of developers realizing they don't understand an important subject because it's separate to their work. Magicroots advice is

by exdsq 5y ago

I think it's just the insecurities of developers realizing they don't understand an important subject because it's separate to their work. Magicroots advice is great. Suggesting devs should be siloed from marketing in the context of a solo developer building products is insane. Signed, an insecure developer with bad marketing skills

oblio 5y ago
The reality is that a lot of developers like to build just for the sake of building. This can lead to the "if you build it, they will come" mentality. Or worse, "we'll build it and we don't care if they come (and if they do come, they'd better RTFM!)" mentality. A huge amount of developers just want to be shielded from any kind of customer interaction, and I'm not talking about call center support.
- lmarcos 5y ago
  > The reality is that a lot of developers like to build just for the sake of building. Very true. I build for the sake of building in my free time. > Or worse, "we'll build it and we don't care if they come... True as well. If I am working on a personal project is because I believe it's the best project ever conceived (obviously I know I'm wrong, but there is always "what if I'm not?!"). > A huge amount of developers just want to be shielded from any kind of customer interaction, and I'm not talking about call center support. But if we are talking in the context of developers working for companies (not developers working on their personal projects) then the only responsible person of working on features no one will use is the project manager (or product owner): they own the product, they decide what comes next (with the help of devs).
  - oblio 5y ago
    There are plenty of companies where developers go partly rogue. Or work on behind the scenes stuff with little oversight and unclear actual benefits. Some developers are actually good at promoting their initiatives.

by exdsq 5y ago

oblio 5y ago

The reality is that a lot of developers like to build just for the sake of building. This can lead to the "if you build it, they will come" mentality. Or worse, "we'll build it and we don't care if they come (and if they do come, they'd better RTFM!)" mentality. A huge amount of developers just want to be shielded from any kind of customer interaction, and I'm not talking about call center support.

lmarcos 5y ago
> The reality is that a lot of developers like to build just for the sake of building. Very true. I build for the sake of building in my free time. > Or worse, "we'll build it and we don't care if they come... True as well. If I am working on a personal project is because I believe it's the best project ever conceived (obviously I know I'm wrong, but there is always "what if I'm not?!"). > A huge amount of developers just want to be shielded from any kind of customer interaction, and I'm not talking about call center support. But if we are talking in the context of developers working for companies (not developers working on their personal projects) then the only responsible person of working on features no one will use is the project manager (or product owner): they own the product, they decide what comes next (with the help of devs).
- oblio 5y ago
  There are plenty of companies where developers go partly rogue. Or work on behind the scenes stuff with little oversight and unclear actual benefits. Some developers are actually good at promoting their initiatives.