3 ms·
> Why must every engineer have an opinion on every technical decision if there are no hard requirements? This isn’t what anyone is suggesting. Committing does
by Aurornis 2y ago
> Why must every engineer have an opinion on every technical decision if there are no hard requirements?
This isn’t what anyone is suggesting.
Committing doesn’t mean everyone needs an opinion on everything.
> It seems pretty clear to me that not every engineer must have an opinion on every technical decision to which they should commit when sometimes
Again, not what’s being discussed.
You don’t need an opinion on everything.
Your team does need to commit to something and move on.
The phrase “disagree and commit” is commonly used when engineers have opinions on everything and are struggling to commit.
Committing != having opinions on everything.
- CharlieDigital 2y ago> This isn’t what anyone is suggesting. Did you read the article? > Some engineers think it’s a virtue to remain non-committal in technical discussions. Should our team build a new feature in an event-driven or synchronous way? Well, it depends: there are many strong technical reasons on each side, so it’s better to keep an open mind and not come down on either side. This strategy is fine when you’re a junior engineer, but at some point you’ll be the person in the room with the most context (or technical skill, or institutional power). At that point, you need to take a position, whether you feel particularly confident or not. That is the very first paragraph of the article. Take up your complaints with the author of the article; not me!
- lcnPylGDnU4H9OF 2y agoI'm not sure how that paragraph gave you the understanding that "every engineer must have an opinion". It explains that the most senior/influential/knowledgeable engineers must have an opinion because they're the ones making the decisions. In that context, the decision is the opinion; not having an opinion is the same as not deciding, which is obviously bad for the person/people responsible for deciding.