Zikeji

I've seen it a few times in passing and always assumed it was like, a tech demo or proof of concept.

I've had bad tinkering break my system before, but never had an update break it irreversibly. The closest would actually be on Silverblue itself, when an update to the kernel was using different signing keys that cause the system not to boot. Fortunately it was simple, I selected the previous deployment and I was in (on a non versioned OS I would have selected the previous kernel which most are configured to retain the last few). A quick Google revealed Ublue had a whole kerfuffle and after verifying it was legit, I enrolled the new certs into my MOK.

Although one time on Arch I had installed an experimental version of Gnome from one of their repos, and was pleasantly surprised when that version finally released and I removed the experiment repo and did an update absolutely nothing at all broke. Nothing.

This consternation is definitely common. It's hard to apply skills to something with no long term impact of benefit. I've improved my skills by finding stuff I can help on in the communities I participate in.

It's natural to be overwhelmed, so deciding on a project does scope what you can learn, but a hard part is architecting the foundation of that project.

Introducing new features to an existing project is a great way to get your feet wet - it has multiple benefits, for one of you do take a position as a developer in the future, you likely won't be architecting anything initially, primarily improving on existing projects. So participating in OSS projects is a similar mechanism to that - you have to learn their codebase to a degree, you have to learn their style and requirements, etc.

Even if you don't ultimately contribute, it's still a learning experience.

I'd rather just write it out. I've never used snippets or macros per say, but I do make liberal use of regex replace and multiline cursors lol. Writing out a bunch of getters and setters? Regex!

I did try LLM tab auto complete and while sure, it did suggest some stuff that was useful (after refactoring it), the amount of time I spent WTF'ing some suggestions it made wasn't worth it.

I find more benefit from asking an LLM about something I'm undecided or confused about, and while it's never given me a good enough answer, it has stirred enough creative juices in my brain to help me along lol.

Edit: sorry for the dupes. When Eternity said it failed the send I took that at face value.

I specifically avoided saying they did because I wasn't knowledgeable on the topic. But I agree, I could equally be accused of being disingenuous by phrasing it in a way that could lead people to assume they use closed loops.

I did look those up, and while evaporation cooling isn't the only method used, it also doesn't evaporate all the water each pass, only a portion of it (granted "a portion" is all I found at a quick look, which isn't actually useful).

I do agree though, the water usage is excessive, and when though that water only "changes forms", it's still removes it from a water source and only some of it may make its way back in.

It's the first thing I thought of when the articles about the generative AI polluting itself started coming out.

Yeah the article is disingenuous at best. There are many things wrong with generative AI, but this is just a lousy approach.

If I make a PC, put in a water cooling loop, and use it to run an LLM - sure, water is circulating, but that water isn't just vanishing lol.

Yeah, the generative AI pollution feels alot like the whole steel thing - since the nuclear tests it's been impossible for new steel to not be slightly radioactive, which means if they need uncontaminated steel they get it from ships that sunk before those.

LUKS, or anything that relies on the server encrypting, is highly vulnerable (see schizo@forum.uncomfortable.business's response).

Your best bet would be encrypting client side before it arrives on the server using a solution like rclone, restic, borg, etc.