Alt account of @Badabinski

Just a sweaty nerd interested in software, home automation, emotional issues, and polite discourse about all of the above.

  • 0 Posts
  • 22 Comments
Joined 4 months ago
cake
Cake day: June 9th, 2024

help-circle
  • I was looking for this comment so I can vent my extreme irritation to the world.

    God, can this concept please die already‽ If you want to put solar panels where the cars/trains are, just 👏 fucking 👏 put 👏 them 👏 on 👏 top👏

    Do not put them on the ground where they will get smushed and covered in dust and snow and dirt. do not. Just make a little roof for the train tracks/road/bike path/sidewalk/game trail/snail raceway and then put the panels on top of the roof and then if you’re feeling fancy angle the panels to point towards the sun and if you’re feeling really quite fancy then you can use bifacial panels to capture the backscatter from the ground and shit and then we can all be happy. solar ground no, solar roof yes, ground no roof yes. do not play the trolley problem with solar panels on the railroad tracks. we have been doing solar energy for decades and have fucking minmaxed this shit so why are they still trying to do this just STOP.

    Fuck.

    Person I’m responding to, please know that none of this is directed at you. I’m just sour right now and should get off the internet.




  • Ugh, I hate ChatGPT. If this is Bash (which it is, because it’s literally looking for files in a directory called ~/.bashrc.d), then it should god damned well be using syntax and language features that we’ve had for at least twenty fucking years. Specifically, if you’re writing for Bash (and not POSIX shell), you better be using [[ ]] rather than [ ]. This wiki is my holy book I use to keep the demons away when writing Bash, and it does a simply fantastic job of explaining why you should use God damned double square brackets.

    ChatGPT writes shitty, horrible, buggy ass Bash. This is relatively decent for ChatGPT (it even makes sure the files are real files and not symlinks), but I’ve had to fix enough terrible fucking shitty AI Bash to have no tolerance for even the smallest misstep from it.

    Sincerely, A senior developer who is known as the Bash wizard at work.

    EDIT: Sorry, OP. ChatGPT did not, in fact, write this code, and I am going to leave my comment here as a testament to what a big smelly dick I was here.


  • Yeah, I’ve been wondering how the fuck they pulled this off. If it turns out that the only pagers that exploded belonged to Hezbollah members, then that would signal to me that this was done entirely digitally.

    I’ve heard that batteries (can’t remember if it was laptop or phone batteries) contain the energy of a small grenade, but getting it to release that energy all at once without physical access is absolutely fucking wild and has serious fucking implications for device security.

    EDIT: To avoid spreading misinformation, I’m providing this edit to say that the batteries absolutely were not the cause of the explosion. This was a supply-chain attack. Explosives were inserted into the pagers. The batteries in these pagers cannot be made to explode like this. I was overly excited when I made this comment.



  • Badabinski@kbin.earthtoMemes@lemmy.mlawHell Naw
    link
    fedilink
    arrow-up
    1
    ·
    25 days ago

    Hopefully we’ll be able to find a working one soon :( our emissions here are exclusively OBD2 based for anything 1996 or newer. I’ll probably do what some other folks have recommended and try to “remanufacture” one myself.

    EDIT: no idea why my client decided to post my comment twice.



  • Badabinski@kbin.earthtoLinux@lemmy.mlGoldilocks distro?
    link
    fedilink
    arrow-up
    26
    arrow-down
    8
    ·
    25 days ago

    For me, it’s Arch for desktop usage. When I first started using Arch it would not have been Arch, but now it’s Arch. The package manager has great ergonomics (not great discoverability, but great ergonomics), it’s always up to date, I can get a system from USB to sway in ~20 minutes (probably be faster if I used the installer), it’s fast because it doesn’t enable many things by default, and it’s honestly been the most reliable distro I’ve ever used. I used to use OpenSUSE ~10 years ago, and that broke more in one year than Arch has in ten.

    I personally feel like Arch’s unreliable nature has been overstated. Arch will give you the rope to hang yourself if you ask for it, but if you just read the emails (or use a helper that displays breaking changes when updating like paru) and merge your pacnews then you’ll likely have a rock solid system.

    Again, this is all just my opinion. It’s easy for me to overlook or forget all of the pain and suffering I likely went through when learning how to Arch. I won’t recommend it to you, but I’ll happily say how much I’ve come to enjoy using it.




  • Badabinski@kbin.earthtoMemes@lemmy.mlawHell Naw
    link
    fedilink
    arrow-up
    25
    arrow-down
    1
    ·
    25 days ago

    Seriously. The ECU in my partner’s truck decided that it was done with magic smoke and Marie Kondo’d that shit out, leaving her stranded. Her truck is an old 2002 Dodge Dakota that we’ve been nursing along while the used car market cools down (we want to get her something small and fuel efficient, but cars cost too damn much). Back in 2000 or 2001, some bean counter at Dodge decided that the company really had to cheap the fuck out with their ECUs for the 2002 model year. Because of this, any 2002 Dodge truck has either had its ECU replaced or is a ticking fucking time bomb.

    What’s even better is that nobody makes these shit-ass ECUs anymore. The only replacements you can get are remanufactured units, and it’s highly likely that you’ll get at least one dud before you can find anything decent. We’ve been a tiiiiiiny bit less lucky than that, meaning we’re on our 13th ECU. Our mechanic has gone through everything else to make sure there’s not something external that’s exploding the ECUs, and he hasn’t found anything. Over the course of like 9 weeks, we’ve completely deleted the stock of these stupid things in Utah and all of the surrounding states. We’re now ordering one from Florida that’s been remanufactured by a different company which hopefully won’t grenade itself.

    Fuck American car companies, and apologies to anyone who’s currently having a hard time sourcing an ECU for a 2002 Dodge Dakota. We screened all the bad ones out for you. The only good part about all of this for us is that our mechanic isn’t charging us for anything more than one ECU replacement. The damn truck has been in the shop for 9 weeks, and we’re only going to pay like $1000.



  • I wrote a comment about this several months ago on my old kbin.social account. That site is gone and I can’t seem to get a link to it, so I’m just going to repost it here since I feel it’s relevant. My kbin client doesn’t let me copy text posts directly, so I’ve had to use the Select feature of the android app switcher. Unfortunately, the comment didn’t emerge unscathed, and I lack the mental energy to fix it due to covid brain fog (EDIT: it appears that many uses of I were not preserved). The context of the old post was about layoffs, and it can be found here: https://kbin.earth/m/asklemmy@lemmy.ml/t/12147

    I want to offer my perspective on the Al thing from the point of view of a senior individual contributor at a larger company. Management loves the idea, but there will be a lot of developers fixing auto-generated code full of bad practices and mysterious bugs at any company that tries to lean on it instead of good devs. A large language model has no concept of good or bad, and it has no logic. happily generate string- templated SQL queries that are ripe for SQL injection. I’ve had to fix this myself. Things get even worse when you have to deal with a shit language like Bash that is absolutely full of God awful footguns. Sometimes you have to use that wretched piece of trash language, and the scripts generated are horrific. Remember that time when Steam on Linux was effectively running rm -rf /* on people’s systems? I’ve had to fix that same type of issue multiple times at my workplace.

    I think LLMs will genuinely transform parts of the software industry, but I absolutely do not think they’re going to stand in for competent developers in the near future. Maybe they can help junior developers who don’t have a good grasp on syntax and patterns and such. I’ve personally felt no need to use them, since spend about 95% of my time on architecture, testing, and documentation.

    Now, do the higher-ups think the way that do? Absolutely not. I’ve had senior management ask me about how I’m using Al tooling, and they always seem so disappointed when I explain why I personally don’t feel the need for it and what feel its weaknesses are. Bossman sees it as a way to magically multiply IC efficiency for nothing, so absolutely agree that it’s likely playing a part in at least some of these layoffs.

    Basically, I think LLMs can be helpful for some folks, but my experience is that the use of LLMs by junior developers absolutely increases the workload of senior developers. Senior developers using LLMs can experience a productivity bump, but only if they’re very critical of the output generated by the model. I am personally much faster just relying on traditional IDE auto complete, since I don’t have to change from “I’m writing code” mode to “I’m reviewing code mode.”


  • They need to do what MacOS and Linux have done. There are safer ways to interact with and inspect the running state of the kernel in those operating systems (eBPF for Linux, a bunch of APIs I don’t know much about for MacOS). Software needs a way to do the shit it’s doing, you can’t just turn it off and provide no alternative.

    If Microsoft provides a safe API, then Wine can translate calls to that API and approximate the same degree of protection for Linux boxen.

    I also agree with the other person, you should still be allowed to fuck around with the kernel on your own box. Major software vendors should be discouraged from writing shit that directly runs in ring 0, but end users should be allowed to do whatever.


  • The tiered storage stuff is pretty cool. You can say “I want this data on this disk, so if I get a cache miss from a faster disk/RAM it’ll come from this other disk first.”

    I believe it also has some interesting ways of handling redundancy like erasure coding, and I thiiiink it does some kind of byte-level deduplication? I don’t know if that’s implemented or is even still planned, but I remember being quite excited for it. It was supposed to be dedupe without all of the hideous drawbacks that things like ZFS dedupe have.

    EDIT: deduplication is absolutely not a thing yet. I don’t know if it’s still on the roadmap.

    EDIT: Erasure coding is deffo implemented, however.


  • Badabinski@kbin.earthtoLinux@lemmy.mlHyprland is now fully independent!
    link
    fedilink
    arrow-up
    60
    arrow-down
    4
    ·
    edit-2
    2 months ago

    What if you need to file a bug? What if you have a question on the config that’s not easily answered by the docs? If you never, ever find bugs and never, ever have questions, then sure, separate the two. There are genuinely people like that, but they’re not common. If you’re one of them, then I’m genuinely glad for you.

    My opinion is this: You use software. You don’t use people, but you sure as hell rely on them.