3 ms·

I recently had a discussion with a very senior developer about a project he'd been asked to do. It's a 6+ month effort and he's just getting started. The projec

I recently had a discussion with a very senior developer about a project he'd been asked to do. It's a 6+ month effort and he's just getting started. The project is to be delivered to a customer, but the customer has not been engaged and does not know we are working on it. I asked the dev how he'd feel if he completed the project and the customer said, 'Nah, not interested, thanks anyway.' His response: 'As long as I get a paycheck, who cares.' Not sure exactly why, but that just doesn't sit well with me.

brudgers 10y ago
The advantage of senior developers is that they're more likely to have realistic expectations, do what they do without unnecessarily riding an emotional roller coaster. With experience in any profession it becomes obvious that every project doesn't turn out as imagined. What is the developer supposed to say about a project that was instigated without their input and without the input of the potential users and is presented up front as a six month slog before reality doubles or triples it? Would, "When it's canceled, I'll mope for a month and come in hung over everyday while looking for another job" be a more inspiring answer? A better question might have been, what do you think about this idea?
dragonlord 10y ago
It doesn't sit well with me either.
- sharps_xp 10y ago
  My idea of a great programmer (non-founder) is one who can execute and deliver the product that his employer wants, which is what the employer thinks is what the customer wants. Let me provide the reverse perspective as a programmer. If I'm a great programmer and you've paid me for my skills as a programmer, the I'm going to trust that you know what you want me to build. Programmers don't have time nor should care to talk to customers unless I'm a founder. In my opinion, it's the employers job to mitigate the risk of the customer not buying the final product. Sure, the 'who cares' attitude doesn't feel right but If you ask all our applicants that question you're just separating them between those who know to lie to get the paycheck and those who are just honest about wanting the same paycheck.
dontJudge 10y ago
> just doesn't sit well with me. Your point of concern should be with management, not the developer. But you only talk about the developer?
jupp0r 10y ago
What should he say? He would probably feel like updating his LinkedIn profile.
tbendixson 10y ago
Sheesh. Have we really gotten to a point where a job can't be a job? I would love to make my own games all day long, but I'm not financially independent yet, so I work for other people. Sometimes their projects work out. Sometimes they don't. I definitely feel bad when they don't, but I also do the practical thing and keep moving forward with my life. There comes a point, after years of experience, where you just have to shrug your shoulders and accept that you aren't the one running your clients' show. You can provide feedback. You can be there when they need you. You can do everything in your power to make it a success. But it's not your thing until you own equity in it. The emotional separation is 100% justified.

brudgers 10y ago

The advantage of senior developers is that they're more likely to have realistic expectations, do what they do without unnecessarily riding an emotional roller coaster. With experience in any profession it becomes obvious that every project doesn't turn out as imagined. What is the developer supposed to say about a project that was instigated without their input and without the input of the potential users and is presented up front as a six month slog before reality doubles or triples it? Would, "When it's canceled, I'll mope for a month and come in hung over everyday while looking for another job" be a more inspiring answer? A better question might have been, what do you think about this idea?

dragonlord 10y ago

It doesn't sit well with me either.

sharps_xp 10y ago
My idea of a great programmer (non-founder) is one who can execute and deliver the product that his employer wants, which is what the employer thinks is what the customer wants. Let me provide the reverse perspective as a programmer. If I'm a great programmer and you've paid me for my skills as a programmer, the I'm going to trust that you know what you want me to build. Programmers don't have time nor should care to talk to customers unless I'm a founder. In my opinion, it's the employers job to mitigate the risk of the customer not buying the final product. Sure, the 'who cares' attitude doesn't feel right but If you ask all our applicants that question you're just separating them between those who know to lie to get the paycheck and those who are just honest about wanting the same paycheck.

dontJudge 10y ago

> just doesn't sit well with me. Your point of concern should be with management, not the developer. But you only talk about the developer?

jupp0r 10y ago

What should he say? He would probably feel like updating his LinkedIn profile.

tbendixson 10y ago

Sheesh. Have we really gotten to a point where a job can't be a job? I would love to make my own games all day long, but I'm not financially independent yet, so I work for other people. Sometimes their projects work out. Sometimes they don't. I definitely feel bad when they don't, but I also do the practical thing and keep moving forward with my life. There comes a point, after years of experience, where you just have to shrug your shoulders and accept that you aren't the one running your clients' show. You can provide feedback. You can be there when they need you. You can do everything in your power to make it a success. But it's not your thing until you own equity in it. The emotional separation is 100% justified.