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

That’s true. A lot of people think that being customer centric means to exactly do what the customer says. But sometimes you have to say “no” or propose different ways to achieve their goals so you can keep the software architecture halfways clean. Unfortunately it doesn’t help that often engineering is not allowed to or doesn’t want to talk to the customer directly so a lot of these trade offs never get to the customer.


> achieve their goals so you can keep the software architecture halfways clean

That sounds... like a bad decision. We create compromised software solutions to support the business, we don't compromise the business to support the software (unless it involves the safety of others).


You have to have a balance or you will reach a point where the software is so compromised it can’t support the business.


I've rarely seen that happen, but I have seen the inverse (over-engineering) hurt businesses considerably more. I'll stick with the devil I know.




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

Search: