Rendered at 20:38:40 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
mawadev 39 minutes ago [-]
I find it funny how businesses can induce fear in people who think they are losing their jobs to ai. Then they lay people off anyway and make the remaining ones do the work of multiple roles. It is a kind of deadlock coming from stagnation, like how can you be motivated to use AI and make up for its mistakes by working overtime?
agenticworldcup 2 hours ago [-]
There's a subtlety about using AI that can make folks less efficient if they aren't careful.
Since LLMs spit out LOTS of text, a person may waste lots of valuable time simply meandering through responses, and trying to keep it all in their head.
Contrast this to talking to a person who might just say "umm.. no no that's not how it works - because blah".
ofjcihen 53 minutes ago [-]
My personally anecdote on poor LLM usage making things take longer:
I had a side (still work) project I wanted to complete that was extremely simple. In my AWS account create an EC2 image builder pipeline that set up a specific component. Just one, very uncomplicated and documented component.
I figured I’d just have Codex do it. I realized after about 3 days of various back and forth in between other work things that we were somehow stuck.
I figured this must be more complicated than I had imagined so I take a look. No, apparently Codex had failed, made an incorrect assumption as to why it failed (again, documents were provided and dead simple) and then continued trying to fix the issue based on the incorrect assumption.
great_wubwub 4 hours ago [-]
"It appears you've misunderstood. We meant less work _per person for the number of people we have right now_."
Since LLMs spit out LOTS of text, a person may waste lots of valuable time simply meandering through responses, and trying to keep it all in their head.
Contrast this to talking to a person who might just say "umm.. no no that's not how it works - because blah".
I had a side (still work) project I wanted to complete that was extremely simple. In my AWS account create an EC2 image builder pipeline that set up a specific component. Just one, very uncomplicated and documented component.
I figured I’d just have Codex do it. I realized after about 3 days of various back and forth in between other work things that we were somehow stuck.
I figured this must be more complicated than I had imagined so I take a look. No, apparently Codex had failed, made an incorrect assumption as to why it failed (again, documents were provided and dead simple) and then continued trying to fix the issue based on the incorrect assumption.