100% agree on the whole thread
11.12.2025 21:55
👍 1
🔁 0
💬 0
📌 0
100% agree on the whole thread
Developer attempts to replicate "Liquid Glass" in CSS, and once finished realizes what she'd actually created is an exploit for a fundamental, previously unknown, and rather serious browser vulnerability
lyra.horse/blog/2025/12...
"CSS hack accidentally becomes regular hack"
The addendum is a fascinating look into the thought process and misery of reconciling contradicting directives and rules in good faith. Anyone who has dealt with that in real life will be very familiar with this.
Just need to get a programmer with kenophobia and a love for golf, and you will be set 🚀
Kind of sounds like expressing self through expressions consumed vs. Learning about others through expressions consumed
I don't understand how anyone can watch how blatantly Grok is manipulated to answer the way ownership desires it to and then act like the other LLM chatbots couldn't possibly be similarly but less obviously compromised to produce responses in whatever way corporate interests and priorities dictate.
I suppose the closest thing to physical ownership on PC is putting a GOG game onto an external drive.
In recent days, oddly similar AI-generated videos depicting nonexistent Black people accompanied by captions such as “dear white people” and “hit follow if you want peace” have proliferated on TikTok. Here's a look at the spam network posting the videos.
www.conspirator0.com/p/one-ai-gen...
Not ideal. Probably an indicator something is wrong with the class interface. Though, need a tool to do it when you're in a bind and need to ship. Need to be able to honestly know when you're using the tool as a crutch for bad designs vs dealing w/ deadline, and then learn how to do better next time
Personally:
Unit: xUnit
Focusing on higher risk and higher complexity modules first, working down lower as time permits
(Didn't ask, but:)
Integration: xUnit + test containers
Acceptance: SpecFlow and/or xUnit (many other options too depending on solution)
E2E: Playwright
Damn I wonder what it would be like if all religious texts were tracked in public github repos from the start
Now That's What I Call Therapy: Vol 1
Automated volume too. Only need to ask: "Can I have one more dissertation, please?"
When we didn't give documentation, context, or intent to people: things were awful. When we give those things to AI: production popped off. AI is amazing
friday soapbox: as a designer, if you want something to be a skillful action for players, and you want growth in this skill to be very deep/meaningful, then you need to also let players be bad at it. sometimes horrendously bad. players hate this pain, and designers often want to mitigate it away.
I've always thought I'd find the most meaning, fulfillment, joy, satisfaction, and sense of connection interacting with a deluge games that humans had nothing to do with. I can't wait for human creators to be replaced. You know, for efficiency; the ultimate consumption experience
tldr: I know things, you know things, we barely know anything; same as always
Even within a stem field, there's a full range of people: from the brilliant to the ones it doesn't click with at all.
Plus, stem is so vast that anyone can be really good at a single or a few aspects of it and still be awful at all the rest.
I think sometimes that attitude is used to offload responsibility on to someone else, with the justification that they're "smart," so that makes it okay.
On the other hand, it's fine to be impressed with someone grasping something that we don't. But also-also everyone has something like that.
Objectivity, impartiality and balance are all *different things*, and the lazy tendency to treat them as synonyms, and to use partisan balance alone as a proxy for the others, is the root cause of a vast amount of nonsense.
In the Keyboard settings of Visual Studio, the shortcut "Alt+/" has been remapped to VAssistX.RefactorCreateImplementation" in the Text Editor context.
Grumpy Old Man Strikes Back
Some problems are defined by conditional complexity, but many are not. Ideally, we should be modeling code accurately to the problem context - and I know "just get it done" and "I'm used to this way" sometimes, unfortunately, wins out.
Seems like using the right tool for the job. Conditionals offer a lot of flexibility, but if you functionally need to look up a value based on a key, then that extra flexibility isn't needed. A lookup table would make perfect sense. Preferring right tools, no uneeded functionality.
I have this take that I'm struggling to put into words, but I believe when possible, you should prefer maps to conditionals.
There was a talk by Sandi Metz years ago, I'll try and find it, but she says, "I'm condition averse, I want to pass messages to objects" and I think she's right.
10x liability is still 10x I guess 💪
Software companies already don't listen to QA, it's one of the reasons why everything is getting worse
Using AI to do the majority of testing will just make ignoring bugs even easier
www.videogameschronicle.com/news/square-...
"oooo i'd draw that but i can't draw"
brother get this through your head
NOBODY can draw
we are literally
ALL
BULLSHITTING
What the heck is a trampoline, anyway?
The blog post is now live! Come one, come all - enjoy this deep dive that commemorates going down the compiler rabbit hole (twice! in the Paris airport!)
savannah.dev/posts/what-t...
Going to be thinking about this thread for a while