Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> The problem with having UX people on a team is that they need to jusity their existence which they do by change for changes sake.

This can be said just about any profession working in software. The real issue is that nobody wants to accept that software can be finished especially management - because then you don’t have anything to sell.

I wouldn’t be surprised if there were designers who fought tooth and nail against arbitrary changes. Surprise surprise good UX designers understand UX. But its like the developer who fights for keeping the PHP website because it works.

Sorry i just dont like treatment non-programming workers as something lesser. So many software companies are sucessfull despite having fucked up technology (by programmers). And its sucessful only because they have great design or marketing or sales team.



There is a financial incentive for software to not be finished and users would probably complain that the software has not improved enough.

With that said, when you look at Word today compared to 20 years ago the functionality really isn't much different. The main changes are the UX.


Software always has bugs that need to be fixed. It is never finished because it has an infinite number of ways it can go wrong. The same is not true for any of the non-software parts of software design.

If you're a software shop you should have everyone who doesn't write code on a contract and not be afraid to terminate them when the product is mature.


A software can only ever be mature for a period of time. Technology advances, work practices change, and your software should adapt to it. Imagine text editing stopped at Notepad, or image editing at Photoshop 1.

Also, your second paragraph leaks of Americanism and undoubtedly, people are happier and healthier with stable jobs.


And consumers are better off when we don't keep the candle stick maker employed in the led factory.


Not only does that metaphor not hold up (is UX obsolete in your opinion?), it's absolutely false.

This is software after all - surely you're aware how throwing out the old solution and trying to build a "better" one results in a long slog of making the same mistakes the old team/product made and fixed (but could have warned you about if they were kept around).


This is so rich and self-serving it’s hilarious . People that “write code” are just as susceptible to making busywork for themselves.


> should have everyone who doesn't write code on a contract

Does that include tech support? What a horrible world you are creating...




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: