zlacker

>>tablet+(OP)
Can we get a video of a workday conducted by these people?

Unless there's a significant sense of what people are working on, and how LLMs are helping -- there's no point engaging -- there's no detail here.

Sure, if your job is to turn out tweaks to a wordpress theme, presumably that's now 10x faster. If its to work on a new in-house electric motor in C for some machine, presumably that's almost entirely unaffected.

No doubt junior web programmers working on a task backlog, specifically designed for being easy for juniors, are loving LLMs.

I use LLMs all the time, but each non-trivial programming project that has to move out of draft-stage needs rewriting. In several cases, to such a degree that the LLM was a net impediment.

>>mjburg+q4
Not exactly what you're asking for, but >>44159166 from today is not a junior web programmer working through the backlog, and the commit history contains all the prompts.

>>jsnell+c5
Sure, thanks. I mean it's a typescript OAuth library, so perhaps we might say mid-level web programmer developing a library from scratch with excellent pre-existing references, and with a known good reference API to hand. I'd also count that as a good use case for an LLM.

>>mjburg+47
I watched someone do a similar demonstration( >>44159166 )live at an event. They ended up doing something like 3 pull requests to get the original change. Then had to do 4 more to get it to fix and put back things it removed. Not exactly efficient, and it was painful to sit there and be like I could have had it done manually 20x by now while we painfully waited for the AI to do the changes.

I've never been able to get it to work reliably myself either.

The internet just tells me to prompt harder. Lots of "grind-set" mentality energy around AI if you ask me. Very little substance.