4 ms·
> Crisply articulate and build alignment around your decision-making criteria Corporate-speak like that is a recipe for bad outcomes. What engineers need to l
by wombatmobile 5y ago
> Crisply articulate and build alignment around your decision-making criteria
Corporate-speak like that is a recipe for bad outcomes. What engineers need to learn is the same thing corporations need to learn but avoid - plain speaking.
See the Challenger O-ring disaster history for a case study.
- Forge36 5y agoIt could just as easily be "establish the priorities." There's different balances and tradeoffs depending on what's considered the top priority. Or am I misunderstanding what this means when plainly spoken?
- deleted 5y ago[deleted]
- bmeski 5y agoThe goal could be something as simple as, “design a search page.” Product/bizfuck person will re-think autocomplete, client-side rendering of results, want categories of results that don’t exist in the data, dynamism for each user that can’t exist given the data. Developer wants to build search page like every other one so that we can get to market faster and move onto something that will actually affect the business. Everyone has different priorities but the engineers are usually based in reality as we have to actually make the f’ing thing.