518
Watching the Generative AI Hype Bubble Deflate
(ash.harvard.edu)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 22 Dec 2024
518 points (96.1% liked)
Technology
60082 readers
3204 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 2 years ago
MODERATORS
"Built to do my art and writing so I can do my laundry and dishes" -- Embodied agents is where the real value is. The chatbots are just fancy tech demos that folks started selling because people were buying.
Eh, my best coworker is an LLM. Full of shit, like the rest of them, but always available and willing to help out.
Too bad it actively makes all of your work lower quality via the "helping".
Just like every other coworker, it’s important to know what tasks they do well and where they typically need help
Lmao your stance is really "every coworker makes all product lower quality by nature of existence"? Thats some hardcore Cope you're smoking.
Every coworker has a specific type of task they do well and known limits you should pay attention to.
Yes and therefor any two employees must never be allowed to speak to each other. You know, because it makes all of their work worse quality. /s
That's quite the extreme interpretation.
I'm a lead software dev, and when deadlines are close, I absolutely divvy up tasks based on ability. We're a webapp shop with 2D and 3D components, and I have the following on my team:
That's across two teams, and one of the senior FEs is starting to take over the other team.
If we're at the start of development, I'll pair tasks between juniors and seniors so the juniors get more experience. When deadlines are close, I'll pair tasks with the most competent dev in that area and have the juniors provide support (write tests, fix tech debt, etc).
The same goes for AI. It's useful at the start of a project to understand the code and gen some boilerplate, but I'm going to leave it to the side when tricky bugs need to get fixed or we can't tolerate as many new bugs. AI is like a really motivated junior, it's quick to give answers but slow to check their accuracy.
This bro should find a new career, they're completely inept.