I read your reply as the scenario from GP is unlikely to happen in practice or has low impact. To me it seems you need to make frequent backups of "your" data to have a copy of it.
Can i run multiple PDSes with my own single identity to not give one provider exclusive power over access to "my" data?
True. i didn't mean "not terrible for employees" i meant "not terrible for company goals". Yes, these are intertwined, but assuming not everyone quits over introducing AI workflows it could make Microsoft a leader in that space.
I find these tools super awesome, but i never use them beyond trying them out once, because they don't usually come with coreutils or something like that.
Haven't found a way to use these tools in a user-local way.
For my own homemade tools, i put the binary in my dotfiles and they end up in .local/bin and i can use them by default. I can do that because I don't need to update them.
The value is in leadership, and being able to avoid certain classes of bugs from appearing in the first place. Troubleshooting just happens to be the skill that allows you to gain the knowledge to lead.
Making troubleshooting skills a profession in itself makes reliability a property of a specific person or team and not a property of the system. The former doesn't scale.
> 1. [...] Every day you stay at Google the more valuable you become.
I'd argue that posts like these decrease the value of Google engineers (and Dell engineers) in my eyes. Maybe that's too shallow though.
I'm involved in hiring a lot and interviewed potential candidates coming from Google and Amazon--none of them seemed like slackers, but also none of them were hired.