[gdev20]

Don't forget that a dev may need another job in the future. And it doesn't help finding one when spending the last 2 years building an app with some "oldschool" tech stack that performs well. Most companies are looking for dev's who worked with the cool fancy stuff like react because that's already the tech stack they are using.

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.

[thinkingemote]

Nothing bad about making something interesting. You would be interested in the end result - but for developers who do this the end result is the technology they produce and not the product that the tech is being used for.

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.

[gdev20]

That's true, in most of the company's I worked (includes the current one) I'm not interested in the product at all. I work there because I can decide which tech stack we use, try and learn the fancy stuff and have some fun building it. Why? Because I can - I am one of the few "good" dev's out there. So many companies are hiring and they take what they can get. And I as a dev can choose where I want to work. And of course I choose the interesting one. In conclusion there are much more companies hiring then good dev's looking for a job. So the company has to make itself interesting for dev's.

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.

[JohnFen]

> That's true, in most of the company's I worked (includes the current one) I'm not interested in the product at all.

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!

[6510]

That was a funny bit of honesty. You should have stuck with it till then end and tell it like it is: It doesn't work on slightly older devices. Or something like: You really notice things don't work when using a slightly older device.

Jokes aside, I cant seem to find data on the age distribution of interneted computers.

[gdev20]

You are the kind of person who believes that every app should support ie8 and even before that, right? Don't forget to limit your 500ps car to drive only 25mph...

[6510]

It isn't your fault they hire people who don't care about the product. That you pick a tech stack that inspires you is a logical [and predictable] follow up.

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.