LLMs will not lead to AGI.

So we are back to the answer we had before LLMs: We don't know if mankind will ever be able to develop am AGI system.

My parcel was marked as Delivered by DHL, but it was not - I was home, they did not come.

Contacted Alibaba - they say they need info from DHL before proceeding with a refund. Contacted DHL - they say they will only communicate about getting that info with the sender, Alibaba.

Bastards.

More importantly, we should ban medical treatment based on unreplicated research.

It's time to save people from becoming victims of the pseudoscience voodoo of psychology.

The Heart of Innovation ! ... In shoes.

The preamble was so long, I actually gave up and came here for a TL;DR, and here it is ! :-D

Why do some people write blogs as if they're still being paid per word ?!

I have felt this for a long time.

Back in the email days, I used to try and get people to nest their email replies. But that was too much work or too complicated for most people.

Slack was awful for being single-threaded. Is it still ?!

X.com seems to be multi threaded but it is hard to see the threads. I find it unusable for discussions, and only use it as a read-only newsfeed. It would be vastly improved if one could easily follow discussion threads, as per your idea.

I have made an attempt at a solution, https://mudg.fly.dev. I am a solo-dev, and would be interested in feedback/feature requests.

You are asking two very different questions here.

i.e. You are asking a question about whether using agents to write code is net-positive, and then you go on about not reviewing the code agents produce.

I suspect agents are often net-positive AND one has to review their code. Just like most people's code.

It seems that people feel code review is a cost, but time spent writing code is not a cost because it feels productive.

I don't think that's quite it - review is a recurring cost which you pay on every new PR, whereas writing code is a cost you pay once.

If you are continually accumulating technical debt due to an over-enthusiastic junior developer (or agent) churning out a lot of poorly-conceived code, then the recurring costs will sink you in the long run

"review is a recurring cost which you pay on every new PR, whereas writing code is a cost you pay once."

Huh ? Every new PR is new code which is a new cost ?

> Every new PR is new code which is a new cost ?

Every new PR interacts with existing code, and the complexity of those interactions increases steadily over time

They need to make a small diagonal model, 5" screen max, 1/2" thick, PCBs inside a rubber frame ( so no extra case needed ).

Also nice would be replaceable plug-in modules a` la Frame.work laptops.

This looks like Python's pickling: https://docs.python.org/3/library/pickle.html

Not quite the same as the object serialization you'll find in many standard libraries, because xitdb can read/write data incrementally, so you can work with large-than-memory data sets.