Had a terrible experience with warp. I personally don't use warp, but I know one colleague who uses it. One day, he ran `kubectl describe <resource> <resource name>` and warp suggested `kubectl delete <resource> <resource name>` and he pressed enter. He was lucky the resource was not critical and could be recreated without any damage. Think about what would have happened if the same thing had happened for the namespace resource. People go into automatic accept mode after some time, and this is very dangerous when you do anything at the terminal, because there is no UNDO button.

I love warp but I always turned the AI off- the GUI improvements were enough for me. I have maintained a general rule for a long time now that when manual commands are run on production, someone else must be watching what’s going on and approving commands or approve them ahead of time.

Yes there is, Velero.

Yeah it might be problematic, but people make mistakes like this all the time, which is why rm -Rf /home /user/.file is a well known rite of passage.

and this is why you want mfa and gitops with multiple users signing off on a change

I wish this was prominently documented. Most people new to Sidekiq have no idea that the job will be lost forever if you simply hard kill the worker. I have seen a couple of instances where the team had Sidekiq Pro, but they had not enabled reliable fetch because they were unaware of this problem

This only works up to some point. Specially when you become senior, just doing the work will keep you in same position forever. Maybe you will get your annual raise etc, but people who play the game will move up and you likely have to listen and build things the way they want, even if you know the problem space well and have a good solution.