I would say that developers try to make it a fad to keep themselves interested and engaged in an otherwise boring, soul destroying or socially harmful job.
I would say that developers try to make it a fad to keep themselves interested and engaged in an otherwise boring, soul destroying or socially harmful job.
And what is so bad trying to make my job interesting? If it's boring I wouldn't care much about the end result. Just another 9 to 5 job then.
I think it would be one of the reasons why "putting devs before users" happens.
Also - look at the HN Who's Hiring threads. Almost all postings don't talk about the product or their users. They talk about the technology.
But I don't think that's bad at all. With modern devices and Browsers you can't tell the difference between using a framework or not.
This way of thinking would honestly have never occurred to me. If I'm really not interested in the product a company produces, then I don't think that I'm qualified to work there.
> With modern devices and Browsers you can't tell the difference between using a framework or not.
I sure can!
Jokes aside, I cant seem to find data on the age distribution of interneted computers.
I think a lot of people still think things are/should be something like: First the product, 2nd the customer, 3rd the company, 4th the investors and the employees last.
But the reality is often more like: First the investors, 2nd the employees, 3rd the company, 4th the customer, and oh we need some kind of product too!
You get the open floor plan so that the investor can see lots of people working. A nice ping pong table to illustrate the lack of employee equity. A fun tech stack to attract and keep the employees happy. Large expensive chunks of plastic with the company name on it. Great customer service to help the customer with their problems and lastly a product that doesn't work.
Again, I'm not suggesting any of this is your fault. On the contrary, one cant teach passion. You either care about the product or you don't.