That's not making something nobody wants - its making something one person wants a lot :)
On a less happy note, there are definitely jobs I've had where I felt like nobody wanted what I was making and its kind of miserable
On a less happy note, there are definitely jobs I've had where I felt like nobody wanted what I was making and its kind of miserable
I've been on both sides of that, and while I appreciate execs that know how to give a project room to breath and find their footing, I also appreciate execs that know when to tear the bandaid off.
Or they are paid specifically for that, or they just spend they work hours on that.
Hopefully they are not spending unpaid overtime on that (unless they consciously volunteer to help with something important, not with widget marketing)
Dear god, no. I’m paid for it.
It still feels like nobody (except my boss) wants what I’m selling.
Which isn’t exactly true either, but people certainly do not embrace change.
Employees don’t want the process, company wants process. Everyone building these is miserable and usually requirements are to actively make user lives miserable instead of easier.
As I've gone through my career I've focused less and less on some specific language or technology stack that is the flavour of the day, and I get my satisfaction from engineering a robust solution from whatever is the must appropriate technology in that specific case.
Besides, our tastes aren't all that unique.