And then claim is attributed right there:

> The hands-down highlight was the talk by Erik Schluntz: Vibe coding in prod.

> Among other things, he drew an analogy between LLMs and compilers.

There's one in the Musée des Arts et Métiers in Paris — blew my mind!

[^1]: https://en.wikipedia.org/wiki/Cloud_chamber

Edit: turns out people make these at home all the time. Sick!

I built this static tool for analyzing the resulting piles of data:

- Who are my top artists in December, across all years?

- Objectively speaking, what is actually my favorite Big Thief song?

- Why won't the cowards at Spotify admit what I know in my heart is the truth (that I am this year's top listener of the Masonna/Prurient split 'Annihiliationism')?

Your data never leaves your browser. Full source is on GitHub.[^1]

Spotify might take a day or two to generate your export; in the mean time, you can try the tool with my depersonalized demo data (link under the upload widget).

Enjoy!

[^1]: https://github.com/lukasschwab/spotify-explore

Comments URL: https://news.ycombinator.com/item?id=46285058

Points: 2

# Comments: 0

> If `url` [optional] links to where you’re talking about a thing, then `external_url` links to the thing you’re talking about.

I'd be shocked if Atom/RSS didn't have equivalents.

This kind of "repost"-ish behavior may just be obscured in the tools people use to construct feeds, so they remain obscure features of the standards. The designers had syndication in mind, very much like what you're describing — ingesting feeds, reprocessing/mixing/extending them, and exposing the result as another feed.

- NetNewsWire was slick, but wouldn't work on my phone.

- Feedbin was excellent, but eventually I decided to do some subscription cost-cutting.

- Miniflux worked fine, but 1) I found it a pain to set up with remote hosted Postgres and 2) it burned through the Neon free-tier usage limits in a couple days.

So I built one myself and run it on a Raspberry Pi home server.

Made a great little weekend project. The feed standards are known quantities, so a little AI assistance with boilerplate goes a long way.

Deciding you need a new feature and just adding it is refreshing — e.g. I wanted a "read it later" feature like Feedbin's (something missing from Miniflux), and now I have it.

I think of Jeffrey Pfeffer's "social contagion" arguments a lot — first with regards to layoffs[^1], but increasingly also to RTO policies and tracked AI use.

It seems very unlikely execs (esp. in small organizations) are taking the time to read and seriously evaluate research about RTO or AI and productivity. (Frankly, it seems much less likely than them doing serious modeling about layoffs.) At some point, the "contagion" becomes a matter of "best practices" — not just a way to show investors what you're doing, but part of the normal behavior shareholders expect.

Bleak if true!

[^1]: https://news.stanford.edu/stories/2022/12/explains-recent-te...

Comments URL: https://news.ycombinator.com/item?id=43540877

Points: 1

# Comments: 1

> Keep a 'black book' or 'memory book' in each control room, a folder of reports on accidents that have occurred. Do not include falls and bruises, but only accidents of technical interest, and include accidents from other plants.

Are there outstanding technical postmortems with good general lessons for software engineers?

Esp. interested in

- Incidents with software products (we all know Challenger) - Incidents written up officially and publicly - Fun reads

Comments URL: https://news.ycombinator.com/item?id=42311233

Points: 1

# Comments: 0

I wind up feeling grateful for simple interfaces, especially the ones disseminated in the standard library.

Comments URL: https://news.ycombinator.com/item?id=38879164

Points: 4

# Comments: 2

It's up to the podcast producers to decide for/against distributor-exclusivity, determining whether OC has to use YouTube Music.

> The vast majority of folks don't know that they have a choice, let alone that they should find/choose an app.

That's... fine. What matters is whether they do have a choice if they go looking for one — again, that's up to podcasters, not up to Google.

Nothing in this announcement indicates YouTube Music will attempt to control distribution. YouTube might give exclusive content a try (a la Spotify), but — to your point — that won't be a "podcast" in the strict client-agnostic-syndication sense.

As long as podcast creators are publishing mp3s to RSS/Atom feeds, YouTube Music is just another podcast client (like Google Podcasts was) which you're free to avoid.

In one respect this consolidation makes more sense than the Play Music → YouTube Music switch: many podcasts cross-post episodes as YouTube videos and audio-only feeds. If YouTube collates those feeds and lets users select between modes while maintaining a unified "already watched/listened" list... hey, that reflects how podcasts distribute/monetize in practice.

The YouTube Music app was a dismal replacement for Google Music, and never regained features for managing one's own library of uploads. Of course, that's not a problem for podcasts; episodes are already syndicated.

All that said, this still bodes poorly.

Comments URL: https://news.ycombinator.com/item?id=16421641

Points: 121

# Comments: 60

Captchas are certainly not foolproof, but they up the difficulty of running a huge number of phony accounts while having a minimal impact on normal Twitter usage.