My sentiments exactly. Incidentally IMO this is arguably more of an anti-authoritative argument, i.e. down on the y-axis, rather than "left" on the x-axis, of the political compass.
Interesting. It's almost like models don't like being ordered around rudely with this "must” language.
Perhaps what they've learned from training data is “must” often occurs in cases with bullshit red tape or other regulations. "You must read the terms and conditions before using this stuff," or something like that, which are actually best ignored.
> 16. Admitting what you don’t know creates more safety than pretending you do.
> Senior engineers who say “I don’t know” aren’t showing weakness - they’re creating permission. When a leader admits uncertainty, it signals that the room is safe for others to do the same. The alternative is a culture where everyone pretends to understand and problems stay hidden until they explode.
It's interesting to contrast this with Sean's statement here www.seangoedecke.com/taking-a-position/
> At that point, you need to take a position, whether you feel particularly confident or not.
> If you don’t, you’re forcing people with less technical context than you to figure it out themselves
To square the circle, I think the lesson is hide uncertainty to higher-ups, but don't to peers/ other ICs.
Of course, the challenge is that often, unfortunately, both the manager and the other ICs are in the same meeting.
Probably this is one justification of one reason why I hate meetings that include managers.