setVeryLoud(true);
He / They
Software Developer
- 0 Posts
- 51 Comments
setVeryLoud(true);@lemmy.cato
Open Source@lemmy.ml•Looking for Ethical & Privacy-Respecting Free or freemium AI Alternatives
1·2 days agoSounds like another human brain, hired and paid legally and with consent. Should tick all your boxes besides free. You gotta break ethics for free.
setVeryLoud(true);@lemmy.cato
Linux@lemmy.ml•Killed by Ubuntu, Linux Mint is Bringing This Classic Feature Back
4·10 days agoLinux S2deep killed my laptop battery after only a year of use and I had to get a new one.
Either it dies in my backpack within hours or I just don’t use my laptop within the next 24 hours and it goes flat.
I had to install Windows on that thing because I would always open it to find it dead.
setVeryLoud(true);@lemmy.cato
Linux@lemmy.ml•Killed by Ubuntu, Linux Mint is Bringing This Classic Feature Back
3·10 days agoIt actually wakes on a timer
Definitely a “holding it wrong” or “you’re using Fedora” type of problem.
I really like systemd’s user services.
setVeryLoud(true);@lemmy.cato
Linux@lemmy.ml•Linux 7.4 Sound Changes Merged: "The AI Flood Continues"
61·18 days agoI don’t know what you’re trying to say, sorry
setVeryLoud(true);@lemmy.cato
Linux@lemmy.ml•Linux 7.4 Sound Changes Merged: "The AI Flood Continues"
6·18 days agoding ding ding
setVeryLoud(true);@lemmy.cato
Programmer Humor@programming.dev•Anon died on the "clang format bad" hill
2·19 days agoSmall print is never in your favour
setVeryLoud(true);@lemmy.cato
Linux@lemmy.ml•Linux 7.4 Sound Changes Merged: "The AI Flood Continues"
42·19 days agoThey’re talking about people who are “anti AI slop” which is a weird stance to take. Slop bad. LLMs are just tools, which can be misused, but slop always bad.
setVeryLoud(true);@lemmy.cato
Linux@lemmy.ml•Linux 7.4 Sound Changes Merged: "The AI Flood Continues"
271·19 days agoOh it’s already easy. You start asking the submitter to explain the code. Sometimes it’s just visually obvious, too.
I’ve always had the opinion of it not being slop if you:
- Take ownership and fully understand the code
- Make it look like a human wrote it, in other words, scrutinize, re-factor and re-format the code for legibility, performance and maintainability before submitting your patch
This effectively forces you to do research to properly understand how your patch is implemented and puts you through the mental exercise of cleaning up the code. It also more often than not mostly replaces the code the LLM generated anyway, making it yours.
I say all this as someone who turns around a lot of PRs at work for being slop. Come back to me when you can take ownership of your git blame.
setVeryLoud(true);@lemmy.cato
Programmer Humor@programming.dev•Anon died on the "clang format bad" hill
7·20 days agoAdvertising is education with misinformation
setVeryLoud(true);@lemmy.cato
Linux@lemmy.ml•I built a GPU-accelerated wallpaper engine for Wayland in Rust — Wallr 🚀
2·22 days agoDid you basically bang rocks together until it seemed to work?
Did you do a code review? That code is horrendous, I would not run that on my machine as a constantly running piece of software that renders my wallpaper.
Also, Crimestoppers just announced that the database of all tipsters and tips for the past 25 years has been leaked.
setVeryLoud(true);@lemmy.cato
Programmer Humor@programming.dev•You just sit in a chair and watch
8·28 days agoBeen using meat proxy for a while now, even used it while training someone lol

Everyone is set up to receive faxes. Not everyone is set up to understand faxes.