Hacker Newsnew | past | comments | ask | show | jobs | submit | evnu's commentslogin

The pun in this follow-up makes the whole mixup worthwhile: https://www.bbc.com/news/articles/cn4n4l1yyvro

"'We're not going to run from it': Sydney Marathon laughs off medal error"


I guess they are laughing it off because it was another Allianz sponsored stadium depicted, and they got the OK from Allianz to make the joke as it is free attention.

If the AI design had chosen a non-Allianz branded location I bet the response would be different.


The race has nothing to do with the stadium, other than running past it. They don’t have to get permission from anyone. Also, there’s no evidence that AI was involved, it could have just as easily been some designer googling for “Allianz Stadium” and illustrating the first thing that came up.


Years ago I was doing internal login pages for pay day loan insurance saas. Decided to put their logos to avoid mixups. Just googled. One was named Vision, copied logo from https://www.visions.ca figuring they did land on the side. Couple years later I realized my mistake & fixed, nobody else had said anything


I'm very sceptical they paid a designer to redraw all these.


Feels kind of pathetic high-schooler level response... "oh well, we're just going to laugh it off, please join us. Enjoy your sloppily* made medal!"

* whether AI-assisted or just lazy human slop that went unnoticed up all the chain.

My own footnote reminds me of this other slop: https://www.theguardian.com/world/2026/jun/06/starbucks-sout...

> It turned out some managers who approved the campaign never opened the email attachments showing the marketing material.


For me, if it's worth thinking about it, it's worth writing it down. Doesn't matter if it's a todo list I just came up with, a system diagram, whatever I am currently working on, or thoughts on a human interaction I just witnessed. The act of writing it down guides me in my thinking.


"perhaps even why it was necessary at all" not being asked anymore is what I fear as well. Stumbling over problems repeatedly gets attention to architectural defects. Papering over the faults with a non-complaining AI buries the defects even deeper, as the pain of the defects isn't felt anymore.


Uiua is the first one that made array languages "click" for me due to the formatter.


Sometimes it works to find a solution which makes the life of teams easier and comes with an additional gain in security. That can potentially be sold more easily to the team then, as you are solving a problem the team actually experiences.


I wondered about that as well while looking into the http handler. I think a missing space between method and path overruns the buffer (haven't tried running it though).


Maybe because aging is non-linear.


Yeah that could be. I need to adjust my mindset around the changes.


Some years ago, I started to use FIXME to indicate that something is blocking the PR and needs to be done before merging, and TODO if something can be done at a later point in time. Then, CI only needs to grep for FIXME to block merging the PR, which works for practically any language. Works pretty well for me, maybe that tip can help others as well.


> Instead you should use high quality sources, then ask the LLM to summarize them for you to start with (NotebookLM does this very well for instance, but so can others).

How do you determine if the LLM accurately reflects what the high-quality source contains, if you haven't read the source? When learning from humans, we put trust on them to teach us based on a web-of-trust. How do you determine the level of trust with an LLM?


> When learning from humans, we put trust on them to teach us based on a web-of-trust.

But this is only part of the story. When learning from another human, you'll also actively try and devise whether they're trustworthy based on general linguistic markers, and will try to find and poke holes in what they're saying so that you can question intelligently.

This is not much different from what you'd do with an LLM, which is why it's such a problem that they're more convincing than correct pretty often. But it's not an insurmountable issue. The other issue is that their trustworthiness will wary in a different way than a human's, so you need experience to know when they're possibly just making things up. But just based on feel, I think this experience is definitely possible to gain.


Because summarizing is one of the few things LLMs are generally pretty good at. Plus you should use the summary to determine if you want to read the full source, kind of like reading an abstract for a research paper before deciding if you want to read the whole thing.

Bonus: the high quality source is going to be mostly AI written anyway


Actually, LLMs aren’t that great for summarizing. It would be a boon for RAG workflows if they were.

I’m still on the lookout for a great model for this.


We found Erlang to be the right choice at small scale. Namely, we used it in iot applications, where the self-healing property of proper supervision trees resulted in a very stable implementation. We also saw the same benefits in the cloud part of our application. No complicated k8s setup, just simple supervisor trees.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: