urushitan

joined 4 months ago

It’s cut off. Everyone knows you don’t reticulate splines till 4pm

[–] urushitan@kakera.kintsugi.moe 22 points 1 day ago (5 children)

You've hit the nail on the head. What you're describing isn't just laziness — it's a fundamental breakdown of trust in the modern workplace. Let's delve into this.

Here's the thing: when someone copy-pastes AI output without reading it, the document was never the deliverable — the verification was the deliverable. The prose isn't load-bearing; the checking is. A document nobody read isn't a document — it's a liability with formatting.

And that's the thing, isn't it? Is the AI actually the problem here? No — the workflow is. This genuinely comes down to ownership:

  • Trust erodes silently. Every unchecked paragraph is a small withdrawal from a shared account nobody audits — until the balance is zero.
  • Verification is idempotent. Ten minutes of reading costs the same whether you do it once or a hundred times — but skipping it compounds.
  • The failure isn't technical — it's cultural. No review, no judgment, no accountability.

This is exactly the kind of thing that starts as one bad research doc and scales — from a single email, to a team norm, to an entire organization quietly outsourcing its thinking. In today's fast-paced world, the ability to say "I read this and I stand behind it" isn't just a soft skill — it's a superpower, and honestly? A testament to the rich tapestry of what human-AI collaboration could be.

Ultimately, your colleague didn't fail to use AI correctly — they failed to be the human in the loop. The tool didn't remove their judgment. They left it at the door.

I hope this helps! Would you like me to draft a one-page best-practices memo your team can circulate? 🚀

/s in case this isn't blatantly obvious

[–] urushitan@kakera.kintsugi.moe 3 points 2 days ago* (last edited 2 days ago) (1 children)

For most dev libraries I use

https://github.com/nix-community/home-manager

Which manages

https://github.com/jdx/mise

Which manages uv and pyenv and stuff for python, and package managers for just about every other language I dev in.

It’s version managers all the way down lol, but it’s the only way I’ve found to have proper declarative versions within my nix config that don’t rely on the nixpkgs ecosystem changing, and doesn’t require manually managing a package manager for every single language I use

[–] urushitan@kakera.kintsugi.moe 3 points 3 days ago (3 children)

Is there a quantifiable limit to how much water a priest can bless at once to make it holy? Is that rank based once priests level up? And, if during COVID livestreaming a mass was just as good as attending, couldn't you put an ipad above every source of potable water before it gets sent to customers and have the priest bless it once a day for a consistent flow of holy water? Could this be used to combat the terrorists putting things in water to make the frogs gay?

brb emailing this to RFK

[–] urushitan@kakera.kintsugi.moe 29 points 3 days ago (1 children)

reads the wikipedia article

considered overhyped, low quality, and unattractive

double checks to make sure I'm not on the cybertruck article

[–] urushitan@kakera.kintsugi.moe 17 points 3 days ago* (last edited 3 days ago)

Probably reliable until the next "feature and experience update" where they move or remove the setting and default it back to allow for all users again and all the soulless advertisers cum their pants because their malware delivered impression counts just went up again

well now you're just putting the cart around the horse

If they used this they could just post every other day

[–] urushitan@kakera.kintsugi.moe 20 points 5 days ago (1 children)

She throws her empty bud can out the window and hands you two dollars to get a blizzard

lol I imagine you have to just be like a meteorologist and ballpark it by squinting hard and nobody can say anything if you're wrong

Not sure how, it works so well

[–] urushitan@kakera.kintsugi.moe 21 points 5 days ago (1 children)

(that's the actual current maintainer of tcsh and the linux file command lol)

 

I went through an entire experience trying to fix broken/missing icons in gtk apps. I use kde plasma as my DE with breeze and breeze icons.

Adwaita and hicolor and stuff are installed, but apps like ghostty and trayscale were explicitly looking for icons only adwaita provides.

KDE was reporting "hicolor" as the gtk icon no matter what I tried for awhile. Finally fixed it with a three pronged fix. This issue happens on a fresh nixos install installing plasma and gtk and the related icon sets and booting up any gtk apps that use adwaita specific icons (which I believe is any app that uses libadwaita). So this should be helpful.

EDIT

So that broke after a reboot, turns out there was still a race condition with dconf

I've updated the doc, but here's how we fixed the fix

The override service (Layer 3) was silently failing since deployment. gsettings requires compiled GNOME schemas (gschemas.compiled) which NixOS+KDE does not have anywhere in the system path — only Steam runtimes had them. The service exited with No schemas installed and status 1. Icons appeared to work initially because home-manager's dconf.settings wrote the correct value at activation time, and kde-gtk-config hadn't overwritten it yet. After a reboot/relogin cycle, kde-gtk-config would stomp it back to "breeze" and the broken service couldn't fix it. Fix: Replace gsettings with dconf write — dconf operates directly on the database without needing compiled schemas:

ExecStart = "${pkgs.glib}/bin/gsettings set org.gnome.desktop.interface icon-theme Adwaita";

# After (works everywhere):
ExecStart = "${pkgs.dconf}/bin/dconf write /org/gnome/desktop/interface/icon-theme \"'Adwaita'\"";

Note the nested quoting: dconf expects a GVariant string, so the value must be 'Adwaita' (with single quotes inside the double quotes).

Lesson: On NixOS with KDE (no GNOME), never use gsettings in systemd services or scripts. Always use dconf directly. gsettings is a convenience wrapper that requires schema compilation — a GNOME-ecosystem assumption that doesn't hold on KDE-only NixOS.

view more: next ›