[jvanderbot]

The thing is, tab complete using LLMs is really great. But I still read it, then press tab, then press enter, then type a few chars, then wait.

Sometimes I get 1 good line from that. Sometimes I get 30. Usually I get 10 bad lines and have to type a bit more to coax out 8 good ones.

It just looks faster but typing was NEVER the bottleneck for coding.

Where it really flies, though, is building tooling around a well known API. FML if I ever have to write AWS CDK or AWS API calls without an LLM again. You're looking at ages of reading through really bad docs to get it going.

For that, which is a 1% task of convenience for most jobs, I can use most LLM output verbatim. But that's like I said less than 1% of the job, and only then when the core software is done.

[pama]

Did you notice how much better things are today (eg Claude Sonnet 3.7) than they were 1 year ago? Don’t you expect things will not improve in the next year? Even R1, a public weights model, can add huge value when left to code in a loop.

[bccdee]

> how things were 1 year ago

Not a substantial productivity multiplier.

> how things are today

Somewhat better than before, but still not a substantial productivity multiplier.

> Don’t you expect things will not improve in the next year?

I expect they'll be marginally better than they are now, but still not a substantial productivity multiplier.

"A huge paradigm shift is just around the corner" is a very popular narrative & it almost never bears out.

[moltar]

Hm, I’m a CDK pro (4y of full time experience). I used all LLMs, except latest Claude model. All were bad in my estimation and just got in the way. I don’t use them for CDK code anymore.

[jvanderbot]

Yeah! That's exactly the thing. It's passable for novices and bad for experts. But I don't need expert level CDK I need an instance to start up. Hate it or love it that's all I need.