A software developer and Linux nerd, living in Germany. I’m usually a chill dude but my online persona doesn’t always reflect my true personality. Take what I say with a grain of salt, I usually try to be nice and give good advice, though.

I’m into Free Software, selfhosting, microcontrollers and electronics, freedom, privacy and the usual stuff. And a few select other random things as well.

  • 0 Posts
  • 230 Comments
Joined 5 years ago
cake
Cake day: August 21st, 2021

help-circle
  • Lmao. First, everyone is right. Go is serious. An Zig as well. And a bit niche.

    Furthermore: Yes. Unless you like learning curves as steep as a brick wall… You should probably start with something beginner friendly.

    And you should get some kind of book to learn it. That’s easier and faster than poking around and learning things in random order.

    As an adult, just skip the programming languages made for children. And skip the crazy ones like PHP. Go for something that is both useful and doesn’t come with 5 bazillion things to learn at once, and as many exceptions to those rules.


  • We’re mixing up two things here. There’s valid criticism. And there’s the people who want to unleash some social-media style shitstorm. The latter show up in large groups and add some unsubstantiated comments, lots of emojis and drown any kind of conversation. But that doesn’t really take away from the valid criticism. For example a maintainer shouldn’t tag a version and release it, when it’s not ready to be released. That’s the 101 of software development. You can expect as much. Because the “bleeding” thing isn’t really how it works. Once there’s a new minor release tagged by the devs, it’s supposed to be picked up by the distro maintainers and get into any distro’s repositories. Doesn’t matter if it’s Arch unstable or Debian stable. They don’t want bugs and security vulnerabilities in their distro, either. Especially not when it’s 6(!) CVEs! And the Debian dev’s in fact reacted to this. And they even backported stuff to oldstable so the people who run the rock-stable stuff from 3 years ago get the patches! So it really doesn’t matter… Run a bleeding edge distro, or a stable one and don’t update it for 2 years, you’ll be affected by this both ways.




  • Thanks. Yeah, I’ve never looked into code quality of many tools I use on a regular basis. So far, rsync has served me well. I’ve been using it at work, at home, for larger amounts of data… Without major hiccups. And we kinda need something like this. It’s a bit of a shame how many essential software projects at the foundation of many things struggle being maintained. My distro has openrsync in the repository. Seems just that that software project is also a one-man-show.

    (Btw, Firefox Translate for the win, I don’t really need a big LLM to translate stuff.)



  • hendrik@palaver.p3x.detoFuck AI@lemmy.worldAI in marketing?
    link
    fedilink
    English
    arrow-up
    5
    ·
    edit-2
    3 days ago

    I see it as well. Your random low-spec computer will now be a somethingsomething AI laptop. Your software and products AI powered and your company AI first. Could mean anything. Maybe they slapped a label on it because it uses maths. Or they added an API. Or maybe it actually uses some modern form of AI. Or it’s the same thing as before. It’s a marketing term, everything needs to “have” AI because it’s modern and maybe still has some futuristic connotation for some people.



  • Yeah, there’s several silly metrics for management to judge programmers. It’s mostly because management needs some oversimplification, because they have no clue what programmers do all day.

    Most common one is “lines of code” (LoC) written in a day. Of course you’re making the company more money if you write more code. That’s your job after all, right? Right??? …Of course that punishes people who write efficient code. Who think first and then come up with a smaller, better to maintain version.

    It’s similar with speed. But just tell the programmers what to do! It’s easy to get 80% the way with 20% the effort. That’s how it always works. Your programmers can do that, just write it into the project specification.

    But to be honest, the major time factor isn’t writing code. It’s all the project management. Misunderstandings, specifications which change over time. Additional requirements after the fact. That’s the major time waster in software projects. Typing down the code takes time as well, but it’s usually not where projects go sideways.

    And use some good frameworks. Leverage someone’s wisdom. Also a major time waster if you wrote code for 2 weeks and find out you’re using the wrong framework and need to start over.

    (Oh boy, and please don’t take the advice to send in half-baked PRs. Yeah, that might look like you’re done sooner. But that’s gonna waste somebody else’s time. And it’ll inevitably return to you and then you’re gonna put in some more time anyway. And you’re gonna waste some more time on arguing about details, changing around stuff… Just get it done on the first try, without any additional back and forth. And returning to each problem three more times. That’s the way to move quick. The outlined way is again how to make management happy. They LOVE to see a PR early and then a lot of activity in the comments. Looks like it’s complicated and people are very busy. But they’re most likely only adding noise and unnecessary back and forth. It’s just… if you just get done with it, quick and without any fuss, nobody will notice.)









  • Difficult to tell. I don’t see anything too obvious or offensive in the commits. They also write like a human in the associated pull requests. Not sure what Claude’s role is here. Also the added code comments are kinda on point, use contractions… Not really what I’d expect from an AI.

    Is there more info on this? A blog post or some statement by the project? At first glance this doesn’t look to me like other vibe-coded projects.




  • Yeah, I don’t think lumping together all these cases is a good idea. There’s legit cases like AI induced psychosis. In which a chatbot directly contributed to deaths, likely even directly caused them. On the other hand a case when a murderer asks what happens if you mix benzodiazepine with alcohol, and the chatbot says it can lead to death… Or if it’s possible to keep an unregistered firearm at home… Well, clearly the murderer already made up their mind and out of some kind of stupidity, they’re bouncing ideas. All the AI does at that point is gather evidence. So it’s doing a good and legit job? I mean I know something that’s far worse and that is: murder mystery stories and movies. NCIS… Shouldn’t we outlaw those? Those are probably planting new ideas into people’s minds… Whereas ChatGPT only served as some poor-man’s Google here.

    On the flipside we’re probably forgetting about the hundreds(?)/thousands(?) of other cases who are on the brink of AI psychosis, or unwell and harmed by (and because of) AI. They’re not dead (yet), but probably not okay either. And pumping out some random number like 33 and setting random standards to qualify is probably doing them a disservice. Or even something fairly simple like being amongst the 30% of staff being fired because of AI, is far worse than it reading back the package insert of some medication.

    (Also, please don’t commit suicide on a railway. That’s horrible. And every commuter hates it. And I heard the train drivers hate it as well.)