I'm not sure about the x, but the first thing that arises from that is, I feel like in my case it's way higher than 2.

The 2nd thing is, how do I measure that.

---

In my case, the details of my work (Kinda DevOps, kinda Senior Dev) makes it that having an LLM to do the heavy lifting allows me to do things not only faster, but better, and across domains I do not hold expertise on.

An example of the effect of LLMs in my daily work is that I'm in the middle of a PHP upgrade for a rather large legacy application, and the "heavy lifting" is really out of the scale, letting me concentrate on what really matters, while at the same time if I do keep "the harness" tight I'm certain the results are the correct ones. Also correcting course is just as cheap.

Not having to worry on the tooling on exchange has the incredible desirable result of my velocity being incomparable to what it was before.

Then we have the side effect of how easy to do transfer knowledge: Rather than telling the QA guy how to do the work specific for this task, I defined a set of files (.md documents, skills, an off-the-shelf customised MCP server) that assist QA into doing the work in a way that helps me do my job better and faster.

There's also a clear possibility that what I'm doing will expand to the rest of the team I am in, completely altering the way in which we approach development.

If we take 'x' as 'mileage', yours might vary. Mine has, and I'm baffled at the positive net results I AM getting.

Also, this what I do (coding?) is extremely fun again.

Being able to work close to the speed of thought is the best high.