this post was submitted on 21 Feb 2025
426 points (98.9% liked)
Technology
63082 readers
3596 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 other!
- 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
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I want a fucking human who can quickly help me solve my issue. I don't want to spend hours looking through "could be" problems. If you manufactured the software then your engineers understand it... Your end users only know how to use it the way they need to use it not all the options and variables.
The ultimate answer:
They have been making these things for decades, they know how to make them better, they know how to make them more durable, they know how to making them even simpler to use and fix, they choose not to, for profit. That should be structurally discouraged.
Charge the manufacturers for the FULL, REAL environmental impact of shipping materials and end of life disposal of their products. Yes, that cost will be passed to the consumers, as it should be. It also rewards sale of more durable goods.
Lol at the notion that you'll get to speak to any engineer when your machine breaks. Best they can do is a call center in India getting paid minimum wage that follows a script and circles around a bit between them until you either give up or they RMA your stuff to feed you a bill later for repairs.
Ah I see the misunderstanding, the engineers were sacked after they finished writing the code.
Of course they didn't leave any documentation because management said that writing it was a waste of time
I see we have the same managers. Were you also advised that public facing databases were better than an API in a VPC and that 1 password shared among colleagues is easier than managing credentials?
Don't worry, I found a new gig starting in a few weeks (out of the pot into pan )
Just hardcode the DB credentials in your client? Stop making things complicated. ~/s~
Won't someone think of the shareholders!
How about a bot that types slowly, so it can have time to consider what it's going to say? Or perhaps a web page with an "Analyzing issue" status bar that takes several minutes to complete, because computers just do better if they're given time to work on a problem?