Original Comic: https://thejenkinscomic.wordpress.com/
this post was submitted on 31 May 2024
12 points (100.0% liked)
linuxmemes
21355 readers
1214 users here now
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Unhelpful Linux User Archetypes:
The Configurator: All problems are configuration problems. The fact that a user has a problem means they configured their machine incorrectly. All help requests are an opportunity to lecture others about configuration files.
The lumberjack: Insists on logs no matter how simple or basic the question. "How do I get the working directory in the terminal?" -Sorry, I can't help you unless you post your log. "What does the -r flag do?" -You need to post a log for me to answer that question. "Is there a way to make this service start at boot?" -We have no way of knowing unless you post your log. When a user posts their log, the lumberjack's work is done. No need to reply to the thread any further.
The Anacdata Troubleshooter: Failed to develop a theory of mind during childhood. Thinks their machine is representative of all machines. If they don't have an issue, the user is lying about the issue.
The Jargon Master: Uses as much jargon as possible in forum posts. If a user doesn't know each and every term, that's on them. If you did not commit to mastering every aspect of a piece of software before asking for help, were you even trying to solve the problem?
The Hobby Horse Jockey: All problems are caused by whatever thing the contributor does not like. Graphics driver issue? Snaps. Computer won't post? Obviously, Snaps. Machine getting too hot? Snaps. Command 'flatpack' not found? Oh you better believe snaps did that.
The Pedantfile: Gets mad because everyone asks their questions the wrong way. Writes a message letting the user know they asked their question wrong. Message usually appears within a minute or two of someone providing a solution to the user.
The Repeatophobic: If a question vaguely reminds them of a previously posted question, they become enraged and insist the new thread be locked.
It's infuriating how many times I've seen a locked thread with no answer linking to a similar yet different problem that doesn't solve my issue.
These types exist for most any technical problem. The last one is the whiny one who also slams someone with a solution they don't approve of. Even if the solution satisfies the person asking for help or perhaps because it satisfies them.
Bonus points if the lumberjack doesn't specify what logs they want or how to get them.