Night update, generated 2026-09-28.
15 new stories since Lunch.
Sources: Hacker News, Lobsters
HN: 109 points, 28 comments (discussion)
Sources: Hacker News, Lobsters
HN: 88 points, 26 comments (discussion)
Sources: Slashdot
Sources: Hackaday
Sources: Slashdot
Sources: Hackaday
Sources: Hacker News
HN: 357 points, 372 comments (discussion)
Reading the code does not mean you understand the code. One lesson that experience in software gave me: I never understood the code. You think it works a certain way, until you find out that it doesn't. What LLMs make possible is for me to say: find out all the ways this thing works. Analyze the di...
Sources: Slashdot
Sources: Hackaday
Sources: Hacker News
HN: 304 points, 199 comments (discussion)
I was reflecting on this on Saturday in an unformed way, trying to trace the lineage of a decision made at work. The code change itself doesn't specifically matter. But suffice to say, it was about an AI feature in one of our products. The code was stamped by Claude driven by a prompt. The prompt wa...
Sources: Lobsters
Sources: Slashdot
Sources: Hacker News
HN: 259 points, 171 comments (discussion)
Pelicans. Sonnet 5.5 has the same problem as Opus 5.5: on "max" thinking effort it burned through 128,000 thinking tokens (taking 15 minutes to do that) and ran out before it had produced the final SVG. https://tools.simonwillison.net/markdown-svg-renderer?url=ht... Here's how the thinking effort le...
Sources: Slashdot
Sources: Hacker News
HN: 224 points, 65 comments (discussion)