2 ms·
>Being aligned with teammates on what you're building is more important than building the right thing. Goodness this is incredibly naive. It can only be true
by astura 7y ago
>Being aligned with teammates on what you're building is more important than building the right thing.
Goodness this is incredibly naive.
It can only be true only if youre working without customers or stakeholders and who the hell works that way other than hobbyists and startups that are indiscriminately wasting other people's money? The vast majority of software I've written (I'm outside the valley) is written for actual paying customers, and it must be "the right thing," ie, exactly what they paid you to build.
Beyond that, if you're, for example, writing an emulator and the emulator works different than the system it's emulating that's a failure no matter how "aligned" your team is. Nobody will buy it and nobody would even use if you gave it away.
- C4stor 7y agoExcept that for a lot of developers, "the right thing" has nothing to do with what customers want, but rather with language used, libraries used, CI/CD setup, monitoring active... So many technical aspects that sometimes have nothing to do with the customer wants. And that's where being aligned makes sense.
- sime2009 7y ago> Goodness this is incredibly naive. Actually it demonstrates hard earned wisdom. A team which isn't aligned will only produce a mess regardless of whether their end goal was the right thing. An aligned team may miss the target but they will be in a position to correct themselves and pursue the target.