• 16 Posts
  • 2.54K Comments
Joined 11 months ago
cake
Cake day: March 23rd, 2025

help-circle






  • Says someone from a country where the word for people from my home town is used to mean “penis”.

    That’s the thing: if you don’t consider racism to be a bad thing, using racist terms isn’t done to show anything.

    To get back to my original example: Using “wiener” to mean penis is deeply offensive to people from Vienna, because in German it just means “Person from Vienna”. But people from Vienna aren’t a group that’s “protected” by anti-racism, and thus people commonly use it. They often don’t even know that the city of Vienna exists, let alone that it’s called Wien and that people from Wien are called Wiener, and that the sausage is named after that city.

    So they happily use the word “wiener” to mean “penis” and sometimes they even use it as a generic derogatory term: “You are such a wiener”.

    In that context it’s not surprising that before anti-racism became a thing people would just use racist terms for every-day items like food.


  • I fear not so. Maybe for easy stuff. But when it comes to actual troubleshooting, Lemmy is severely limited by its tiny user base.

    (There’s only about 40k monthly active users on Lemmy, and that number includes bot accounts. For comparison, that’s fewer active users than the Crackberry forum or the LTT forum. Reddit has over a billion of daily active users, so around 25 000x as many as Lemmy.)

    Chances are there’s nobody on Lemmy who uses the same hardware, the same distribution and the same DE as me, so if I need help debugging an issue that’s specific to my combination, I’m out of luck.

    Even on Reddit the same is true for many issues. While there might be someone with my exact combination who might even know the answer, that person first has to stumble across my post among the millions of posts that are created every hour on Reddit.

    So chances are if you ask a deeper question than “How do I copy files” you will not get an answer. Instead you likely will just get snark and “RTFM noob!”

    In fact, even though I have been using Linux for well over a decade now, I ran across a problem I couldn’t debug: Games would run fine on my 4070 today, but they’d randomly slow to a crawl (multiple seconds per frame) the next day. I’m a Linux software developer, so I know how to go about this. Reboots and all the usual stuff didn’t help. Logs didn’t show anything relevant. Google didn’t help either. I asked on Stackexchange, but the question was closed as duplicate to an entirely unrelated question. By the time I got it reopened, it was so far down the queue that it didn’t get any answers. Asking on Reddit just got me “Lol, noob, RTFM, works on my machine”-type of answers.

    So I bit the bullet after about a year of getting nowhere and asked AI, and the first answer got me to the right track.

    Turns out, flatpak keeps its own copy of the Nvidia driver. This version needs to be identical to the system driver version. If it’s not, the GPU isn’t used at all and instead it falls back to software rendering. So if I do dnf update and it updates the GPU driver, it breaks the performance. Running flatpak update && reboot fixes it again. So any time I ran dnf update without flatpak update && reboot after it, it would break the performance. And I often ran flatpak update first.

    AI reall can help debugging weird issues.



  • Technical debt is a management term.

    The reason we use it is to tell non-technical management people why implementing a simple feature might take an hour on a fresh project and a week on an old legacy project.

    It’s used to tell them why we shouldn’t go with the quickest and dirtiest solution but instead should go with a more expensive proper solution.

    It also tells management why we might have to spend some time imrpoving our code base without any tangible improvements to the customer.

    And because it’s a term that speaks to non-technical management it uses financial language, becausee that’s what they understand. Technical debt means “I am choosing to cut corners today, but we will have to pay up in the future by fixing stuff that wouldn’t be broken if we do it right today.”

    And because it’s aimed towards non-technical management and not towards developers, it’s of course not very specific. Non-technical management doesn’t need to understand about dependency hell, unclean code or bad developer documentation. That’s not their field and it doesn’t have to be.

    The real problem in OOPs example wasn’t that there’s no clear metric or definition of technical debt. The problem was that non-technical managemnt thought that technical debt is an engineering concept instead of a management one, and thought that they themselves were allowed to meddle with it.

    The right way to handle that is to ask the people who are actually impacted by technical debt what they want to improve. Any developer can quickly give you a good list of the most pressing tech debt issues in their code base. No need to pull in someone from outside of the project to make up some useless KPIs that will end up missing critical topics.


    Btw, engineers already have engineering terms for what’s described as technical debt. E.g. “dependency hell”, “low test coverage”, “outdated dependency”, “bad code style”, “unoptimized code” and so on. And since these are engineering terms, they actually have specific meanings and most of them are testable and quantifiable in some specific way.



  • Infinitely far.

    First, actual infinite power is impossible. It violates a bunch of the laws of nature. Not going to happen ever, at all.

    Second, practically infinite power (meaning more power than we could ever use) is also out of reach. Solar/wind is super cheap, but you still need to build and maintain the PV/generators and that will always have a cost. Also, there’s infinitely much we could do with energy, so if energy gets cheaper we will just use more of it.

    If energy was close to free, we’d just replace cargo ships with railguns or something crazy wasteful like that. We’d invest crazy amounts of energy in making things a little bit more comfortable.

    Just look at the current AI craze, or the crypto craze. None of that is actually doing something really necessary, but it makes numbers go up on some billionaire’s charts and thus we waste ungodly amounts of energy into it.

    If it wasn’t that way, and instead we’d keep our lifestyle and just use cleaner energy production to not destroy the planet, we wouldn’t have global warming at all right now. With the lifestyle of the 50s and the efficient tech from today, global warming wouldn’t exist.

    But we like numbers going up and thus we burn more and more energy and having more energy available just means we burn more of it.






  • Smartphone detection cameras are relatively recent and I pointed them out because they are the best solution that exists so far.

    But laws against using your phone while driving, we had them already decades ago, and we had other solutions before the cameras. E.g. placing police next to the highway and letting them pull everyone out who uses their phone. We had that too decades ago. And that too works.

    But it’s not only that. There are posts all the time about Americans being surprised that speed cameras exist, that red light cameras cameras exist, that speed limits are things that can actually be enforced and so on.

    Today there was even a post about some road being restructured with sidewalks, pedestrian crossings and shrubbery, and that was seen as something revolutionary by all the americans in the thread, and not something that the rest of the world has been doing since the 50s and that’s already way outdated compared to what’s happening now.

    The US is a total backwater country where everything that benefits regular people happens 50 years later.