If you're going to use anti-semitic online trolling tropes at least spell them right. It's "Hasbara" and no Israeli under 80 years old uses this word on any day to day basis.
when I asked it how, it mentioned that it knows I live nearby
Did it mention it in its chain of thought? Otherwise, it could definitely output something because of X and then when asked why “rationalize” that it did it because Y
Is “they were bought because they’re Israeli intelligence” the new “Jews control the banking system”? Please update, I’m somehow missing the residuals from both :(
Is it just me or the post and the hn title don’t match? All I see is several paragraphs and a summary to the effect of “managers of managers should trust their decisions to terminate ICs” - no discussion on how to actually manage the ICs you can’t fire as a manager, which is the content the title (“Managing People You Can't Fire”) states
Yes, but it requires a truly disciplined management layer to foster such an environment, e.g. not commenting negatively in 1:1s on the comments of a 3rd party and remediate immediately any such accidental remarks that might hurt the safety to be vulnerable.
I’ve had the same experience, both as IC and a manager. It’s a nice framework, just not for human organizations (KPI for next framework: result in less “no true Scotsman” replies whenever a post details why the framework sucks in their organization)
Establishing AWS identity outside of AWS is a headache, and often comes with a chicken-and-egg problem of needing to possess a secret to show you are allowed to get a secret.
For most stuff here, we can rely on the fact that every connection over Tailscale is encrypted and authenticated to an identity
Mm, okay, but you still have the chicken and egg problem of distributing the creds to join your tailnet.
Isn’t it not that different than distributing aws creds to access secrets manager?