this post was submitted on 20 Dec 2023
159 points (88.0% liked)
Asklemmy
43739 readers
1149 users here now
A loosely moderated place to ask open-ended questions
If your post meets the following criteria, it's welcome here!
- Open-ended question
- Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
- Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
- Not ad nauseam inducing: please make sure it is a question that would be new to most members
- An actual topic of discussion
Looking for support?
Looking for a community?
- Lemmyverse: community search
- sub.rehab: maps old subreddits to fediverse options, marks official as such
- [email protected]: a community for finding communities
~Icon~ ~by~ ~@Double_[email protected]~
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'm interested in where the limits to expectations lie here. I'm not trying to be a jerk when I say this next part but I do worry I may come off that way but I'm trying to figure out the boundaries of what a "reasonable" expectation is so I can make tasks like this easier for my own team (completely unrelated to this project but it's essentially the same problem).
Is it not reasonable to expect people to type into a search engine something like "GitHub help" and then poke around in the links that come up?
.... Well I'll be damned, I tried my own method before commenting, and the first link that comes up is a red herring, how obnoxious. I was hoping it'd be a link to the docs, not GitHub support. I guess I just answered my own question: no that is not reasonable.
As a technical user, I am still at a loss for how to help a non-technical user in an algorithmic way that will work for most non-technical users x.x guess I'll be thinking about this problem some more lol
(I guess I'm rambling but I'm gonna post this anyways in case anyone wants to chatter about it with me)
It's super hard to know this and there won't be a consistent answer because everyone is different. You have to meet people where they are.
I think you did answer your own question on this one. I'll also say that as a somewhat technical user but still not a heavily technical user like some people here, GitHub is a really baffling website. It's hard to even figure out how to download something from it. I would strongly encourage anyone who wants to reach non-technical users to avoid GitHub. It's made for programmers and it doesn't make sense to anyone else without training.
That's fair. Part of my job is converting non-technical users into technical users by teaching them things like problem solving approaches that are supposed to help them teach themselves how to learn whatever they need to actually do their job. I don't teach them what to do, I teach them how to learn what to do.
I agree that you gotta meet people where they're at, but I try to teach them how to poke around any code repo site, like GitHub or gitlab, so they can use it. Usually I point them to the docs and start by pointing out my favorite parts so that they have somewhere to kind of start by themselves, but it is a skill set that can be practice, or at least I am convinced it is.
I'm not very good at this part of my job, but also, no one is, so it's not a bad thing, I just want to do better. I guess I never thought of it from a truly non-technical and not wanting to be technical perspective before. This could be solved by a secondary interface designed specifically for this kind of user. It would not allow code download or interaction, but it would allow for issue logging. I might put this idea in my ever growing project list because it sounds like it would be a useful product...