> I've never seen any tech theme pushed top down so hard in 20+ years working.

> The common theme is C-suite thinks it will save money and their competitors already figured out out, so they are FOMOing at the mouth about catching up on the savings.

I concur 100%. This is a monkey-see-monkey-do FOMO mania, and it's driven by the C-suite, not rank-and-file. I've never seen anything like it.

Other sticky "productivity movements" - or, if you're less generous like me, fads - at the level of the individual and the team, for example agile development methodologies or object oriented programming or test driven development, have generally been invented and promoted by the rank and file or by middle management. They may or may not have had some level of industry astroturfing to them (see: agile), but to me the crucial difference is that they were mostly pushed by a vanguard of practitioners who were at most one level removed from the coal face.

Now, this is not to say there aren't developers and non-developer workers out there using this stuff with great effectiveness and singing its praises. That _is_ happening. But they're not at the leading edge of it mandating company-wide adoption.

What we are seeing now is, to a first approximation, the result of herd behavior at the C-level. It should be incredibly concerning to all of us that such a small group of lemming-like people should have such an enormously outsized role in both allocating capital and running our lives.

I don't understand how all these companies issue these sorts of policies in lock-step with each other. The same happened with "Return To Office". All of a sudden every company decided to kill work from home within the same week or so. Is there some secret CEO cabal that meets on a remote island somewhere to coordinate what they're going to all make workers do next?

> FOMOing at the mouth

This is a great line - evocative, funny, and a bit o wordplay.

I think you might be right about the behavior here; I haven't been able to otherwise understand the absolute forcing through of "use AI!!" by people and upon people with only a hazy notion of why and how. I suppose it's some version of nuclear deterrence or Pascal's wager -- if AI isn't a magic bullet then no big loss but if it is they can't afford not to be the first one to fire it.

At least they are consistently applying this to all roles instead of only making tech roles suffer through it like they do with interview processes

Then, you might even tinker with some AI stuff on your own terms, you never know. :)

Or install a landline (over 5G because that's how you do it nowadays) and call it a day. :-)

> (cc / codex / cursor / copilot (jk, nobody should be using copilot)

I seem to be using claude (sonnet/opus/haiku, not cc though), and have the option of using codex via my copilot account. Is there some advantage to using codex/claude more directly/not through copilot?

The KPI problem is systemic and bigger than just Gen-AI, it’s in everything these days. Actual governance starts by being explicit about business value.

If you can’t state what a thing is supposed to deliver (and how it will be measured) you don’t have a strategy, only a bunch of activity.

For some reason the last decade or so we have confused activity with productivity.

(and words/claims with company value - but that's another topic)

Can I modify your example to:

Demanding everyone, from drywaller to admin assistant go out and buy a purple colored drill, never use any other colored drill, and use their purple drill for at least fifty minutes a day (to be confirmed by measuring battery charge).

It's really cascaded down too.

Each department head needs to incorporate into their annual business plan how they are going to use a drill as part of their job in accounting/administration/mailroom.

Throughout the year, must coordinate training & enforce attendance for the people in their department with drill training mandated by the Head of Drilling.

And then they must comply with and meet drilling utilization metrics in order to meet their annual goals.

Drilling cannot be fail, it can only be failed.

This is literally happening in non-tech finance firms where people in non-tech roles are being judged on their AI adoption.

Some companies swear by this. CP Rail is notorious for training everyone to drive a train.

3. They discovered it's something they can measure so they made a metric about it.

Or it has an annoying learning curve.

That sounds like a lot of work - maybe you could burn some tokens asking AI to write a cron to burn some tokens for you?

That seems just as bad but the opposite direction.

The obvious pulling ahead from early AI adopters/forcers will happen any moment now... any moment

I try these things a couple times a month. They're always underwhelming. Earlier this week I had the thing work tells me to use (claude code sonnet 4? something like that) generate some unit tests for a new function I wrote. I had a number of objections about the utility of the test cases it chose to write, but the largest problem was that it assigned the expected value to a test case struct field and then... didn't actually validate the retrieved value against it. If you didn't review the code, you wouldn't know that the test it wrote did literally nothing of value.

Another time I asked it to rename a struct field across a the whole codebase. It missed 2 instances. A simple sed & grep command would've taken me 15 seconds to write and do the job correctly and cost $~0.00 compute, but I was curious to see if the AI could do it. Nope.

Trillions of dollars for this? Sigh... try again next week, I guess.

Fall behind what? Writing code is only one part of building a successful product and business. Speed of writing code is often not what bottlenecks success.

> I mean get onboard or fall behind, that's the situation we're all in. It can also be exciting.

I am aware of a large company that everyone in the US has heard of, planning on laying off 30% of their devs shortly because they expect a 30% improvement in "productivity" from the remaining dev team.

Exciting indeed. Imagine all the divorces that will fall out of this! Hopefully the kids will be ok, daddy just had an accident, he won't be coming home.

If you think anything that is happening with the amount of money and bullshit enveloping this LLM disaster, you should put the keyboard down for a while.

Anyone with more than 2 years of professional software engineering experience can tell this is completely nonsense.