I’ve been doing this stupid math daily game about making a number out of four fours. The page for it is clearly jank and vibecoded but it’s an interesting concept so I’ve been looking past it.

Well, yesterday’s number (147) was literally impossible. I tried for hours, then started reading math papers about the problem and all solutions I could find had the repeating/overline operator. Which doesn’t exist as an input option on the stupid puzzle site.

My parents are coming over today because their ZorinOS installation suddenly started acting up after an Ubuntu Kernel update. Thanks Ubuntu.

A train that doesn’t arrive at all is also not considered late.

I’ve recently learned that when an experienced doctor administers those tests you also get bonus points for being overly pedantic. As in, if you feel the need to clarify every single question, get frustrated about the questions being too vague or get annoyed at the answer options not being specific enough, that will push you towards the diagnosis even before any sort of score is counted.

Oh, and most people with a false negative on the test get there by assuming that everyone feels like this. “I’m not abnormally sensitive to any sort of material. Just velvet and styrofoam are the worst, but everyone hates those so it’s normal”

Have you ever pressed F12? We technically weren’t allowed to see the config either, but LiteLLM literally returned a users password hash as part of the user data json in the version we were using. It was easy enough to see that it wasn’t salted.
Another fun thing it does is that any user can see their entire teams token spend trough the network tab, even if they technically shouldn’t be allowed to do that. Oh and LiteLLM had a CVSS score 9.9 vulnerability recently where any user with any sort of write privilege (including the “privilege” to change any of your own data, like your password) could just change their own role to admin 🤷

The pure incompetence of that software would be really funny if it wasn’t such a pain in the ass to be the person who has to convince coworkers to rotate compromised credentials…

Even better, LiteLLM does not salt their SHA256 password hashes by default. I had to make a huge fucking fuss over that fact until my org changed the configuration last month. Bet we’re in that leak, with password hashes that are easily cracked with a dictionary.

huh, time for what?

bold to assume company policy doesn’t require the desktop background to be a picture of a concrete wall. Gotta make it feel like you’re about to be executed by firing squad if you don’t generate enough shareholder value.

deleted by creator

It really isn’t hard to get out of a docker container. Especially when its config is vibecoded.

I spent like an hour yesterday bullying Claude out of using a ResizeObserver, Refs and a useEffect construct just to fix the height of a container (there was a bug where the container didn’t properly scale down in height because some weird hard-coded properties in an external component inside of it). I knew that it had to be solvable with just the right css selector, but I was lazy and didn’t want to manually go through the html and figure out which selector on which component would be the right one. And on paper “Go through this massive block of html and check which property is out of place” should be the kind of use case where LLMs actually work. The stupid thing introduced two new different catastrophic failure modes where the entire browser crashed due to excessive rerenders before it found something that even remotely worked. And then I had to spend another hour stripping out unnecessary style properties it glued on while looking for a working solution. In the end, I probably would have been much faster doing it by hand.

based. So glad I moved there recently.

Yeah, when my company first forced Claude on everyone the head engineers managed to negotiate that Claude would only run in a WSL sandbox. But people were lazy, so they just gave that WSL as many permissions as possible (Mounting C directly to it, opening up all interfaces, popping in full-access git tokens etc.). Then management sent out an extremely biased “survey” that has the question “Is having Claude in the WSL inconvenient to you?” and all the lazy bastards said yes. So now management lifted the sandboxing requirement to make work “easier” for devs. In the meantime, the engineers arguing for proper sandboxing are already so worn out from telling people to not intentionally compromise their sandbox that they’ve kinda just given up. Not having a sandbox at all isn’t much more insecure than whatever people are already doing 🫠

Fuck those glasses. But also, my brain can’t let go of the question of “How would I feel if I saw a woman wearing these?”. And honestly I’m not sure??? Like you could make an argument that at least they would deter creepy men?? Anyone got any thoughts on that?

Damn, that’s top-tier schizoposting

loud fan spinning noises

There can be different reasons for different people. I personally have zero fear of being laid off (strong worker protection laws in Germany) and finding a new job this year was surprisingly easy (50-ish applications with no cover letters -> 3 interviews -> 3 offers) and I still feel the exact dread that is described in the article. The industry sucks in multiple different ways rn.

fuck off clanker

Me neither, but I bet it’s still valid JS syntax