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

help-circle




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











  • Judging by skeuomorphic icons that got stuck in the past, they usually get stuck with the last iteration of tech that is single-purpose and unambiguous.

    For example, the icon for “train” is most often a steam train, even though they haven’t been common for a very long time. But there’s nothing else that looks like a steam train, while a diesel/electric train just looks like a generic box when on a small, low-resolution icon.

    The disk icon for saving got stuck because it’s the last piece of storage tech with a clearly recognizable shape. SD cards are just rectangles, hard drives or SSDs also don’t really have a clearly recognizable shape (especially not to someone who has never taking a PC apart).

    But the floppy disk icon won against e.g. drum storage (which is sometimes still used as an icon for databases) or tape storage, because it was newer and more widely used.

    The landline phone icon wasn’t replaced by a smartphone, because the smartphone isn’t single-use. It’s ambiguous what e.g. an app with a smartphone icon would do, since a smartphone can be used for a ton of different things.

    So in short, an icon gets stuck with the

    • newest tech
    • that is single-use
    • that has a clearly recognizable shape

    From then it stops mattering whether the tech depicted is still in use or even known by the youngest generation. It’s now not the “floppy disk icon” but the “save icon” instead.


  • No, it’s not. It’s a misconception on the very fundamental level of the concepts we are talking about.

    Moderating an online forum and state-sponsored censorship are two wildly different things. The former is in many circumstances legally required while the latter is legally prohibited (in most cases).

    Freedom of speech means that the government is not allowed to interfer with your speech (with exceptions). It doesn’t mean that everyone has to listen to your bad takes let alone has to host them on their privately owned website.

    Who does something matters just as much as what is done. Same as you can’t claim that the police is kidnapping you when they arrest you for murdering your neighbour.

    These basics are so basic that it is hard to believe you don’t understand them. If you really don’t understand them, read up on just the very basics of the concept of rule of law and the basic rights one has and how they apply.

    It’s more likely though that you do understand but just want to argue in bad faith, in which case it is not a conversation either.