> OpenClaw gave me the chance to become that super manager [...] A manager shouldn’t get bogged down in the specifics—they should focus on the higher-level, abstract work
These two propositions seem to be highly incompatible
> OpenClaw gave me the chance to become that super manager [...] A manager shouldn’t get bogged down in the specifics—they should focus on the higher-level, abstract work
These two propositions seem to be highly incompatible
Surely you meant "'Benenson' without the “b” in the email, and the hyphenated 'out-look.com' domain"?
To be fair, the problem was probably that particular implementation, but I'm wondering if there's any successful rollout of that model at any significant scale out there.
This location either uses the named locations I have set up in Entra (we use our public IP ranges for it) or it prompts users for their address if isn't sure. https://learn.microsoft.com/en-us/microsoftteams/emergency-c...
1. I don't speak authoritatively and
2. I don't have knowledge of the whole product - there's always a rogue team here and there doing stuff.
We've had that feature turned on at MSFT for some time now. It does not allow your manager to see that you're at Starbucks, at home, on the shitter or anything like that. There's a new toggle in the calendar settings called "Share location with my organization", and the settings are: "all details: building, desk, etc.", "general location: office or remote", "can't view any location information". What it does when turned on is just adding, at the top of your calendar, icons that tell you which of your colleagues are in office, and if they share and you click on someone's picture, what building they're in (when it works).
The whole "it will tell your manager what your wifi is" is just baseless extrapolation, and plainly false from what I can tell.
That would be really helpful.
Why isn't Claude doing all that for me, while I code? Why the obsession that we must use code generation, while other gabage activities would free me to do what I'm, on paper, paid to do?
It's less sexy of course, it doesn't have the promise of removing me in the end. But the reason, in the present state, is that IT admins would never accept for an llm to handle permissions, rotations, management would never accept an llm to report status or provide estimate. This is all "serious" work where we can't have all the errors llm create.
Dev isn't that bad, devs can clean slop and customers can deal with bugs.