Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Please don't post about US Politics. If you need to do this, try [email protected]
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
Tech people presume that normal people think about how technology works
They don't even try to conceptualise how something on their phone gets there from the internet or 'the cloud' - when things stop working they don't think about the fact that their an app on their phone is using a network connection to a router, which distributes an internet service that connects them to a server, that is running a program, on which they have an authenticated account...
They wouldn't even know where to begin with troubleshooting, it's just 'broken' and they get frustrated
Here's the difference you're probably not understanding about your self: people don't need to know everything about everything, and they couldn't if they tried.
A very small part of my job involves lubricating large industrial fans. Easy enough. What grease should we use? Hang on to your fucking panties
Lube or grease? Lithium-based? Urea? Composite? What was used previously? What should have been used previously? Have you ever done sampling? What's the vibration frequency?
Did you know there are people with PhD's in grease composition?
I bet you never even realized that was a thing.
So no, I don't know what TCP/IP means, or what port and protocols are or what the hell a subnet mask is. I don't even know what I don't know. And that's okay, because YOU know. Doesn't make you any smarter than me, any more than it makes a grease expert smarter than either of us.
Nothing I said was critical of anyone, any set of skills, any profession. I'm glad that you have specialist skills, everyone does because no-one can know everything
I was responding to a particular question about technology, and how non-techies approach it. I explained in another comment that this complexity in technology is fundamentally different from many other fields of everyday experience
If the industrial fan stops working, they call you, and somewhere between the power point and the air they want to move is the problem you can fix and diagnose
If someone can't see their cat photos, it could be anywhere from their device to their network, their ISP to the server, the programs on that server, the other server that holds the photos... Like with the fan they know the power is generally ok because the lights didn't go out, but from that point you actually need some conceptual model of the complexity to even know who to call