Arcanoraptor

@AnarchoCatgirlism

The most common design pattern I can find is just recurseUntilSuccess

Makes sense if they vibe coded it. Clankers are scared as hell of any kind of exception; if I had to guess, it’s because exceptions during training probably are penalized. But it’s actually absurd how much they go out of their way to twist their code into little Gordian knots just in case the int the user passed into the function magically stopped being an int halfway through. And we all know how the Gordian knot was “solved” :3

I’ve come to the conclusion that every function you vibe code with these is just more technical debt. Once you’re 20 classes and 2k lines deep into the vibe coding opium, it’s just too easy to let it continue to create a black box for you. Especially if you’re under time pressure to keep moving jiras down the board, and it technically passes your CI tests.

And that works precisely until it doesn’t, and your entire source code gets leaked by a dependency you vibe coded :)

Every time I see a post about Fedi groups, I notice how distinctly flat the names are. What if we organized them into a logical hierarchy? I dunno, maybe…

Comp.* for computer related topics
News.* for world events
Rec.* for recreation (like Games)
Sci.* for things related to science
Soc.* for generic discussion
Alt.* for everything else that doesn’t fit these categories

Then you’d be able join, I dunno, ‘rec.games.zachlikes’ or whatever for puzzle game discussion :3

Help I’m looking at secondhand rack-mounted equipment again

@0x00string@infosec.exchange Magic Snake Theory is just Pascal’s Mugging for millennials :P

Best thing about installing Arch as a kid was learning how Linux works

Second best thing about installing Arch as a kid was learning of the existence of the Arch Wiki. I don’t daily drive Arch anymore, but I use that wiki all the time!