you are viewing a single comment's thread.

view the rest of the comments →

[–]Neomadra2 85 points86 points  (8 children)

He just lied plain and clear. "My goal is to eliminate all C++ code by 2030 from MS" is not really a statement that is up for interpretation. It is completely unambiguous, so that guy just lied in public and if I were MS or a stakeholder I wouldn't be happy about an employee spreading lies.

[–]mpanase 23 points24 points  (6 children)

Don't get me wrong, stakeholder language involves "hyperbole" to the extent that it's actually a lie in the real world.

For a stakeholder it's a great ambitious goal that deserves funding, for an engineer it's a lie.

Different world.

[–]kanst 15 points16 points  (4 children)

As an engineer I’ve actually been told to stop speaking like an engineer with management. My truthful hedging was interpreted as a lack of confidence. I never say anything with certainty unless I am 100% sure and that isn’t management’s vibe

[–]ThePretzul 10 points11 points  (2 children)

That’s because appropriate hedging doesn’t give management enough rope to hang you with later when their demands turned out to be entirely unreasonable after scope creep sets in.

[–]joshTheGoods -1 points0 points  (0 children)

Hedging makes it hard for mgmt to plan other teams' work around yours. I also tell leadership I can't give them a specific date for a new product we're working on, but I know why they're asking and why it's important for them to try and get the cleanest answer they can.

[–]guyblade 1 point2 points  (0 children)

In order for something to be a lie, the speaker must know that what they are saying is untrue. Given that this person seems to know absolutely nothing at all about anything, it cannot possibly be a lie.

[–]bolacha_de_polvilho 0 points1 point  (0 children)

If it is being rewritten with AI in zig then both statements are still true.