cslinuxboyStarlink is already exempt from the FCC router ban. Imagine that...
#Starkink #FCC #RouterBan #Corruption #Trump #nobot #Internet #Musk
| Website | https://birdwainer.net |
Bird Wainer
- 28 Followers
- 100 Following
- 206 Posts
Software engineer and Mediocre Persistent Threat. Known abuser of LLMs. Scream while you still have a mouth.
@tinker AI stands for Assumption Intensifier.
@ariadne One thing that has been consistently underscrutinized with regards to LLMs is the design choice to use a chatbox exclusively. By using a design grammar that has historically indicated that another human is on the other end and not displaying anything but the text coming out of the LLM, providers are tacitly (and sometimes not so tacitly) encouraging users to anthropomorphize a huge file full of floating point numbers. It causes users to over-estimate their capabilities and excuse their flaws to their own detriment and to the advantage of LLM Companies and I find it insidious.
@Ashedryden What is in between a non-profit and a for-profit?
Jack Daniel (often offline)Happy Solstice y'all
Am I the only one waiting for RFK jr. to cut to the chase and announce that it is now HHS policy that correlation **IS** causation and that anyone disputing this fact with concepts like "math" or "science" or "basic reasoning" will be tried for witchcraft?
mirsadra- #Python is written in C
- #Perl is written in C
- #Ruby is written in C
- #PHP is written in C
- #JavaScript engines started in C, now mostly in C++
- #Go was first in C, now written in Go itself
- #C++ compilers are written in C++
- #Swift is built with C++ and Swift (on LLVM in C++)
- #C# runs on .NET, built in C++/C#
- #JVM (HotSpot) is written in C++
Yet, people still doubt the necessity of learning C!
Steve Fenton ➜There's a vibe coding thread where developers are having an epiphany: maybe they should keep old versions of their code around, just in case their latest inspired hack turns everything into digital spaghetti.
Congratulations—they've just discovered their first professional software delivery practice: Version control. That's from 1972.
Next week, they'll revolutionize development by inventing "testing" after their app crashes in production. Again.
@simplenomad I think one of the things that is really hard about it, is that it is being thrown at so many different things. I mean how you handle AI for use as a coding assistant is going to be different from how you handle it as a document summarizer. And when the use case is everything on all of the platforms all of the time it becomes very difficult to think through. Which isn't to say it's insurmountable, just a problem requiring decomposition. I think the first part has to be sitting down with users and saying "We are going to set guidelines for one thing. Tomorrow we can go a different one, but this conversation is just about X." Sooner or later we can figure out the commonalities and start to generalize.