You jest, but companies have sent people home fully paid, because power or internet were down and would be down for an extended period of time. Technically a small number could have kept working on white-boarding design topics, but without access to documentation, existing tickets, it would have been minimally effective.

It's not clear if or when these tools become as essential as power or internet to a developers or admins work, but if they do? Giving everyone a quarter day off at least generates some good-will, unlike forcing them to sit around unproductively because of working hours.

My real world experience of this is that people prefer not to code by hand because it feels wasteful relative to agent speeds, so they find non-coding productive activities such as code/documentation review or usability testing.

What would you do if there is a significant outage in AWS or GCP or Github or JIRA or any other service you use at work? same goes for AI tools as well.

If both of them are down at the same time, I would switch to my Kimi or GLM subscription and keep working. If they fail too, I switch to any number of providers via OpenRouter.

While there is some lock-in for the hardest tasks, for most of what people do LLMs are rapidly becoming a commodity.

In fact, right this minute I have Opus benchmarking Kimi alongside itself to determine which workflows we'll switch to using Kimi by default and Opus as the fallback instead of vice versa. It has already conceded Kimi does better on several tasks.

Those are your tools and if the AI companies have their way, they will be your only tools. Complete dependence on AI is the goal here.

You mean like GitHub?

easy, we will switch to OpenRouter et al.

[flagged]