Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)B
Posts
0
Comments
609
Joined
2 yr. ago

Alt account of @Badabinski

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

  • All of the nice Python build tools are getting slopifed. OpenAI just bought Astral (the folks who make uv and ruff).

  • I gave it no advice, and all I wanted it to do was generate a script to tell me the file type of the newest file in the current directory. It was a very trivial piece of code. Each time it generated something I disliked, I told it "don't do this, reference this guide for the correct thing to do," or "don't do that, do it in such a way that X happens." It was like 20 lines of bash in the end.

    I was expecting it to write me a bash script because that's the example that everyone, without fail, says will work well. "I just used Claude to write a little throwaway script to move some files around" were the exact words a colleague used.

    Bash is a shitty, unsafe language. I don't write large programs in it. I expect "throwaway scripts" to still be written in a way that defends against all of the innumerable shitass foot guns present in the language. Claude was incapable of doing this in a reasonable time frame.

    I also dislike the Python and Go it generated, while we're at it. It produces overly verbose, overly documented, poorly performing code. It was also fucking dog shit at referencing runbooks and documentation in a local folder when I was on call and responding to alerts.

    It sounds like you're quite partial to Claude, and I hope it's been a very good and helpful tool for you. I did not find it to be particularly helpful for me. It was very good at putting me in a sour mood, however.

  • Shellcheck, while good, doesn't capture all best practices in my opinion. There are many items in that doc which shellcheck would happily allow, worst of all being set -euo pipefail.

  • I'll say that during a recent week where I was forced to use an LLM, I found Claude Opus to be extremely poor at referencing this guide: https://mywiki.wooledge.org/BashPitfalls

    it took almost an hour to get Claude to write me a shell script which I considered to be of acceptable quality. It completely hallucinated about several of the points in that guide, requiring me to just go read the guide myself to verify that the language model was falsifying information. That same task would have taken me about 5 minutes.

    I believe that GIGO applies here. 99% of shell scripts on the internet are unsafe and terrible (looking at you, set -euo pipefail), and Claude is much more likely to generate god awful garbage because of the inherent bias present in the training data.

    And as for unit tests? Imo, anything other than property-based testing is irrelevant. If you're using something like Pydantic, you can auto-generate a LOT of your tests using the rich type annotations available in that library along with hypothesis. I tend to write a testing framework once, and then special case property tests for things that fall outside of my models. None of this is super helpful for big ugly codebases with a lot of inertia around practices, but that's not been my environment, thankfully.

  • Where's the CVE? Was there an attempt at responsible disclosure? Was confidentiality breached? Did they coordinate this release with the devs like the dirtyfrag people did? This "announcement" doesn't answer any of these questions and I am frustrated by it.

    EDIT: Ok, there IS a CVE: https://security-tracker.debian.org/tracker/CVE-2026-46300

  • Hardware AFAIK.

  • There are far more bountiful resources to be found, including GitHub issues with concrete examples. I picked that one because I know that all four of the companies listed are problematic. I do not currently have the time to find more detailed links, but they're out there.

  • Current sodium chemistries have a kinda shitty voltage curve. I expect it will get better, but right now a LOT of the power delivery happens with voltages below 3 volts. LFP batteries deliver most of their power at higher voltages which lets you use thinner conductors and cheaper/more efficient electronics.

    Again, not saying that it's necessarily an inherent flaw in sodium chemistries, just that the current generation that people can access and test right now is unsuitable for some tasks.

  • Removed

    One wish

    Jump
  • If I understand it correctly, it's just that any infringement onto the liberties of other sentient beings is not tolerable to people who take it to that degree. To harvest wool, you do have to contain the sheep and potentially put them through experiences they would not choose for themselves. I'm not a vegan so it wouldn't really be right for me to mangle their philosophy any more than I already have, but I believe that's the gist.

  • Removed

    One wish

    Jump
  • Depending on your definition of vegan, wool is also not an option. I'm unsure of how many people take it this far, but I do know at least one person who refuses to use anything that directly derived from an animal.

  • If you get some PETG V0 or ABS V0, that will be perfectly safe and probably up to code. That shit can self extinguish when it catches on fire.

  • Are you going to Walgreens? If so, entering 771 as soon as you hear something will take you straight to a human.

  • Does this mean that they won't have to be packaged in the most infuriating way possible? Current 2032 (and other coin cell) battery packaging is a nightmare to get into and is so fucking wasteful of plastic. Kids just won't stop eating these fucking batteries, so the solution was to fucking entomb them in HIPS or PVC or whatever the fuck.

  • It's such a godsend. I wish people would teach both methods. It's great that the "righty-tighty" thing works for so many people because it's probably much faster than using your hand, but I spent so many years thinking I was shit at mechanical stuff because I couldn't figure which way to turn a screw. I probably wouldn't have a fucking obnoxious complex about it nowadays if I had learned this when I was five.

  • Not everyone has this instinct. There are many people who are unable to differentiate left from right. For those people, this doesn't really work. I'm in my thirties and I still give shitass directions because I suck at telling left from right. I can do cardinal directions pretty well as long as I have a reference like some mountains, but like, I still have to think about left versus right.

    I posted this elsewhere in this thread, but the only thing that's ever worked for me was the right hand rule, where you use your right hand to physically demonstrate to yourself which way a screw needs to go.

    Also, TIL that there's a specific term for this: https://en.wikipedia.org/wiki/Left-right_confusion

  • Reposting this as a direct response to you in case it's helpful:

    Try using your right hand directly to figure out which way to turn a screw. Make a loose thumbs up. Point your thumb in the direction you want the screw to go. The way your fingers are curling is the way you turn your screwdriver. If it helps, try to imagine there are arrows pointing out of your fingertips. Works just like the right hand rule in physics.

    EDIT: here's a picture of what I mean: