Hacker News new | past | comments | ask | show | jobs | submit login

It depends. "Let's change to <new JS framework for no reason>" is annoying. But if you do a little more research and reframe the problem to make it simpler, that's just good senior dev work.

Understanding the problem and finding what the business really needs instead of diving in.




If every suggestion like this came with discussion

- What will it cost

- What problem will it solve

- What advantages will it bring

- What disadvantages will it cause

, then there would be no reason not to bring it up. Maybe I'm just jaded, but when you try to bring up these points, people often (subconsciously?) try to "sell" their suggestion instead.


That sounds like normal work to me. Identify business value, communicate, prioritise, build.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

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

Search: