Balooga

When you create a work using a tool, you own the copyright.

When you create a work using an LLM, there is no copyright.

So then isn't an LLM less than a tool?

In my head "make" implies copyright. If you make it then copyright belongs to you unless you sign that away.

You prompted, the LLM made. The output of the LLM is not eligible for copyright.

You can perhaps copyright the prompt. That you did make.

Not to be an arse, but didn't you have access to Stack Overflow with all questions/answers prior to LLMs?

FYI; In South Africa, the 5 1/4 inch is a "floppy". The 3 1/2 inch is a "stiffy". I don't understand why this isn't so everywhere.

Uh oh. You could be genetically predisposed to have to listen to everyone's problems.

They know, because in their personal capacity, they hate interacting with AI customer service agents from other companies.

But their bonus depends on driving down costs in their company.

In aerospace related industries there is a culture of writing and reading of requirements.

I system engineered for a major US satellite TV provider, and just the specification that defined the protocol for transmitting guide data over the satellite was about 640 US letter pages when printed.

I used to work in Burbank and lived approximately 34 miles away, across Los Angeles. It could take almost three hours for me to drive home on a Friday afternoon on the freeway. This was before Covid, and traffic has only gotten worse.

Costco?

[Edit] -- And I've frequented several independent coffee shops that are cashless.

I like to think back on this scene from Galaxy Quest, when the team sits around the conference table[1].

"I have one job on this lousy ship, it's stupid, but I'm gonna do it! Okay?" -- Sigourney Weaver

[1] https://www.youtube.com/watch?v=W4CgQMJCpZI

That way of teaching got us to the moon, created transistors, produced the internet, smartphones, quantum computers, the very AI that everyone is talking about, vaccines, sent probes into space, cured diseases, fed millions, jumbo jets, basically every single thing that society has come to depend on.

It might be borderline exploitative, but I have noticed that elderly individuals want a "solution" rather than a lesson.

Or they may have just aged out of fucks[1]

[1] https://www.blog.lifebranches.com/p/aging-out-of-fucks-the-n...

My Dad could never build the metal model to understand that common concepts like copy/paste would work almost identically across different native Windows applications; "How do I copy/paste in an email?", "How do I copy/paste in a Word document?", "How do I open a file in Excel?", "How do I open a file in Word?".

The lightbulb just never went on in his head. And this was in the 90s and early 2000s when developers at least used MFC - probably the period of peak UX design.

Things have now gotten so much worse since then. Now, I struggle to remember how to add an attachment in MS Teams, which I use every day.

And is "model collapse" a thing when LLMs are trained on 100% LLM-generated code? Fun times ahead.

There is OpenGOAL[1]. A re-implementation of the language that Naughty Dog used to created Jak and Daxter.

[1] https://opengoal.dev/

Keep in mind that Fielding used his "REST" principles to drive work on the release of HTTP 1.1 in 1999. He subsequently codified these RESTful principles in his dissertation in 2000. The first JSON message was sent in 2001. The reason RESTful is perfectly suited to the WWW is because REST drove HTTP 1.1, not the other way around.

Now days there are just so many use cases where an architecture is more suited to RPC (and POST). And trying to bend the architecture to be "more RESTful" just serves to complicate.

You describe how web pages work, web pages are intended for human interactions

Exactly, yes! The first few sentences from Wikipedia...

"REST (Representational State Transfer) is a software architectural style that was created to describe the design and guide the development of the architecture for the World Wide Web. REST defines a set of constraints for how the architecture of a distributed, Internet-scale hypermedia system, such as the Web, should behave." -- [1]

If you are desiging a system for the Web, use REST. If you are designing a system where a native app (that you create) talks to a set of services on a back end (that you also create), then why conform to REST principles?

[1] https://en.wikipedia.org/wiki/REST

Then that does not conform to the HTTP spec. GET endpoints must be safe, idempotent, cachable. Opening up a site to cases were web crawlers/scrapers may wreak havoc.

There is one reason. The DELETE absolutely must be idempotent. If it's not, then use POST.

Fielding's paper doesn't provide a complete recipe for building self-discoverable APIs.

But it does though. A HTTP server returns a HTTP response to a request from a browser. The request is a HTML webpage that is rendered to the user with all discoverable APIs visible as clickable links. Welcome to the World Wide Web.

The simplest case, and the most common, is that of a browser rendering the HTML response from a website request. The HTML contains the URL links to other APIs that the user can click on. Think of navigating any website.

Can the executive branch force arbitration via presidential order to limit the ability to form class action suites?

The problem I find happening too often is that everything works on the initial install. Then an update comes along and nukes sound. Then a few weeks later a round of updates fixes sound but breaks Bluetooth. Then a few weeks later an update nukes WiFi. Ok, connect via Ethernet. Three updates later Bluetooth starts working again.

Then everything works... until you try to adjust the display brightness.

This on pre-2020 Lenovo laptops.

Africa runs on WhatsApp.

Went to South Africa on vacation last year. United lost our luggage on the first leg of the trip, which then became South African Airways responsibility to sort out because they handled our final leg.

I communicated directly with the SAA baggage agent over WhatsApp. Then communicated over WhatsApp with the courier delivering our bags . Best customer service ever.

Between $3k and $30k to solve a single ARC-AGI problem [1]. Not sure if "100 runs" makes this comparable.

[1] https://techcrunch.com/2025/04/02/openais-o3-model-might-be-...

The library would continue to work but may no longer be usable if other dependencies require a later version of "n" that the abandoned library is incompatible with. Ruby or Python runtimes are the classic example.

I have been involved in numerous "waterfall" software projects and the majority were successful. This is because the "waterfall" process was never as the Agile proponents describe it. Successful "waterfall" projects are always iterative.

You know what didn't work? SAFe Agile.

I don't know. Maybe treat others as you yourself would like to be treated?

"If I Had More Time, I Would Have Written a Shorter Letter" -- https://quoteinvestigator.com/2012/04/28/shorter-letter/

I wish I had the link to the YouTube video where a researcher described one of the main reasons why MYCIN failed. Because when you optimize for number of patients per doctor, it is a lot more cost effective to prescribe a broad spectrum antibiotic that kills all pathogens and move on to the next patient than it is to spend time with one patient and MYCIN to narrow down to the exact pathogen.