Technology

59390 readers

4323 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 1 year ago

MODERATORS

[email protected]

1009

77% Of Employees Report AI Has Increased Workloads And Hampered Productivity, Study Finds (www.forbes.com)

submitted 3 months ago by [email protected] to c/[email protected]

206 comments fedilink hide all child comments

The new global study, in partnership with The Upwork Research Institute, interviewed 2,500 global C-suite executives, full-time employees and freelancers. Results show that the optimistic expectations about AI's impact are not aligning with the reality faced by many employees. The study identifies a disconnect between the high expectations of managers and the actual experiences of employees using AI.

Despite 96% of C-suite executives expecting AI to boost productivity, the study reveals that, 77% of employees using AI say it has added to their workload and created challenges in achieving the expected productivity gains. Not only is AI increasing the workloads of full-time employees, it’s hampering productivity and contributing to employee burnout.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 77 points 3 months ago (21 children)

The workload that's starting now, is spotting bad code written by colleagues using AI, and persuading them to re-write it.

"But it works!"

'It pulls in 15 libraries, 2 of which you need to manually install beforehand, to achieve something you can do in 5 lines using this default library'

[–] [email protected] 35 points 3 months ago (11 children)

I was trying to find out how to get human readable timestamps from my shell history. They gave me this crazy script. It worked but it was super slow. Later I learned you could do history -i.

[–] [email protected] 20 points 3 months ago (1 children)

Turns out, a lot of the problems in nixland were solved 3 decades ago with a single flag of built-in utilities.

[–] [email protected] 3 points 3 months ago (1 children)

Apart from me not reading the manual (or skimming to quick) I might have asked the LLM to check the history file rather than the command. Idk. I honestly didn't know the history command did anything different than just printing the history file

[–] [email protected] 4 points 3 months ago* (last edited 3 months ago) (2 children)

man 3 history

info history

Also, your .bashrc file in your $HOME Dir contains env variables you can set to modify the behaviors of the history function.

[–] [email protected] 2 points 3 months ago (1 children)

I really need to alias man to man -a.

[–] [email protected] 1 points 3 months ago (1 children)

I man -k a lot.

[–] [email protected] 1 points 3 months ago (1 children)

What's that?

[–] [email protected] 1 points 3 months ago* (last edited 3 months ago)

The option -k for the command man allows you to search the manual pages for specific terms.

Similar to the command apropos

Examples of both in the image

[–] [email protected] 2 points 3 months ago (1 children)

Oh I need to learn more

[–] [email protected] 3 points 3 months ago

Honestly, I thought I knew lots.

Then, one day, I decided to read man intro

Then I knew I knew I didn't know much.

I still don't.

But I now have a much better grasp of what/how.

load more comments (9 replies)

load more comments (18 replies)