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

This is far from novel. PMs, devs and architects allow the tech stack to influence product all the time, often on the basis of back of napkin cost-benefit analysis.

In fact, an org that doesn’t define tech constraints is setting itself for overengineering while a disciplined org can use those constraints to drive more, not less, business value.




Influence but not define.

If you tell me we can't hit business objectives because the team wants to use react native instead of swift without a really good reason, it's not going to work.


I suppose you could say the same sentence in reverse? These days you have to support Android and iOS so Swift is only going to get you so far.




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

Search: