this post was submitted on 28 Mar 2024
404 points (97.2% liked)

Technology

59412 readers
3000 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 94 points 7 months ago* (last edited 7 months ago) (11 children)

*bad Devs

Or devs who don't give a shit. Most places have a lot of people who don't give a shit because the company does not give a shit about them either.

[–] Passerby6497 40 points 7 months ago (10 children)

What's the diff between a bad dev and a dev that doesn't care? Either way, whether ist lack of skill or care, a bad dev is a bad dev at the end of the day.

[–] [email protected] 17 points 7 months ago (6 children)

The difference is whether the fault for the leak of your personal data rests with the worker who was incompetent, or the employer who didn't pay for proper secure software.

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

I say fault lies not with only one, but both.

[–] [email protected] 8 points 7 months ago

Depends on the case TBH. If devs barely have time and are constantly crunching due to mismanagement, or are extremely disengaged due to mismanagement, I wouldn't fault them.

Usually it's the lacking processes, though. There are ways to make sure this doesn't happen, and it doesn't depend on the individual, but always the organization.

load more comments (4 replies)
load more comments (7 replies)
load more comments (7 replies)