[redmaverick]

simple reason. I can refactor the codebase in a dozen different ways in a matter of seconds and choose the best one to work on. I can a summon a large volume of unit tests, descriptive logging statements etc. I can also just dump the logs and it will 9/10 times tell you right away what the issue is and how you can resolve it.

i.e basically you can do a lot of work in just a matter of hours. Once you taste the productivity increase by integrating AI into your workflow you will miss it if it is taken out.

not mention you can build all the handy little tools in a matter of seconds that will make your daily life way easier.

[tjr]

Employees have been prevented (by rule) from doing things that would make them more productive for a long time. For a trivial example, programmers who are proficient in Emacs not being allowed to install and use Emacs.

I still fail to see why employees will now choose to disregard this particular rule, and either disobey or quit.

[ParetoOptimal]

> For a trivial example, programmers who are proficient in Emacs not being allowed to install and use Emacs.

I'm not sure how you mean trivial here, but not being able to use emacs isn't a trivial matter to emacs users :)

> I still fail to see why employees will now choose to disregard this particular rule, and either disobey or quit.

I fail to see why employees follow rules that make no sense rather than disobeying or quitting.

[EFreethought]

Honestly, "no Emacs" is one rule that would make me quit.

[ParetoOptimal]

So would I. Funnily enough I thought it might happen at a job in the past so I've thought through the "would you quit if work banned Emacs" question quite a bit.