516
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
516 points (96.1% liked)
Technology
60087 readers
2734 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
I just had to transfer one of my guys out after frequent arguments to do that. I don’t understand - I point out a function that does exactly why he wants, yet he still wants to reinvent it.
I’m dreading when I come back after break. I got 50% a new junior guy who keeps saying he’s a great programmer. No sign of it so far but my management insists I take him on. All he needs to do is expose a new endpoint, wire up functionality that’s already there, and I walked him through it. Should be easy, right? No reinventing the wheel, right?
I do know the feel. I was young once (seems a long long time ago). Reinventing the wheel was fun and challenging. I loved creating libraries. I didn't actually know at the time that there were already existing libraries I could just use, this was the 90s. But it is hard to keep track of what library code exists in a project if you didn't write it. Maybe assign them to review the library code and document it or something. Then they will know what it is at least.