• 0 Posts
  • 9 Comments
Joined 1 year ago
cake
Cake day: July 13th, 2023

help-circle
  • The cyber truck is, at this point, a malfunctioning status symbol. I suppose a 100K truck that sucks at being a truck is intended to communicate the driver is a successful tech guy but, whenever I see one, I think “there goes a rube”. I have a similar reaction when I see those gaudy designer bags or “luxury” branded tee shirts. I don’t think “there is someone who is successful” I think “that person is an idiot.”

    There should be a catchy term for status symbols that communicate the opposite of their intention. Stupidity symbol? Status irony? Status error? None of these really roll of the tongue.


  • JollyG@lemmy.worldtoShowerthoughts@lemmy.worldFEMA camps
    link
    fedilink
    arrow-up
    23
    arrow-down
    1
    ·
    25 days ago

    When bad people do good things they are generally seen as sinister, as if they are concealing a horrible action behind a facade of good will. So if you believe the government is fundamentally evil, and you see it trying to do something good (which is the whole purpose of FEMA) then its actions are going to look sinister to you. So stories about FEMA having camps (at their core, these are stories about the government using the facade of aid and assistance to hide something evil) will make sense to you because they are consistent with your sentiments about the what the government is. So too would stories about FEMA using disasters as a pretext for land snatching or stories about FEMA ignoring people in peril because these are all stories about an evil government. To the extent that they are consistent with your sentiments about the government, they are easy to accept as true, even if they contradict each other.


  • I often have the opposite experience when looking for technical documentation about programming libraries. For example I will be dealing with a particular bug and will google the library name plus some descriptive terms related to the bug, and I get back general information about the library. In those cases, it seems google often ignores the supplemental information and focuses only on the library name as If I were looking for general information.

    What is worse is that the top results are always blog-spam companies that just seem to be copying the documentation pages of whatever language or library I was looking at.




  • 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.



  • Thanks for reaffirming my bias that new cars suck.

    I am really concerned the next car I need to buy, which is probably 20 years off, is going to be this trend cranked to 11. With software and hardware I can find alternatives and hack my way around the “you paid for it, but we own it and can do whatever we want to it” mentality that tech companies push, but cars seem like a whole different world when it comes to the “you paid for it, but we own it” mentality.