# New York Times Editor Stephen Hiltner on the "52 Places to Go in 2026" Page: https://stenobird.com/podcast/out-of-office-a-travel-podcast-629743/new-york-times-editor-stephen-hiltner-on-the-52-places-to-go-in-2026 Text version: https://stenobird.com/podcast/out-of-office-a-travel-podcast-629743/new-york-times-editor-stephen-hiltner-on-the-52-places-to-go-in-2026.md Podcast: [Out Of Office: A Travel Podcast](https://stenobird.com/podcast/out-of-office-a-travel-podcast-629743) Published: 2026-01-27T12:47:58+00:00 Episode link: https://outofofficepod.libsyn.com/new-york-times-editor-stephen-hiltner-on-the-52-places-to-go-in-2026 Audio file: https://traffic.libsyn.com/secure/outofofficepod/Out_of_Office_Episode_218_REVISED.mp3?dest-id=782160 Processing state: not_requested JSON: https://stenobird.com/v1/public/podcasts/out-of-office-a-travel-podcast-629743/episodes/new-york-times-editor-stephen-hiltner-on-the-52-places-to-go-in-2026 Duration seconds: 3074 ## Resource This week on Out of Office: A Travel Podcast, Kiernan chats with Stephen Hiltner, the New York Times editor in charge of this year's "52 Places to Go in 2026." Stephen walks us through this year's top picks and themes. Here's what we cover in this episode: "52 Places to Go in 2026" https://www.nytimes.com/interactive/2026/travel/places-to-travel-destinations-2026.html "Top 10 Reader Favorites from our '52 Places to Go' List" https://www.nytimes.com/2026/01/13/travel/places-to-go-readers-picks.html ## Actions - request_transcript: `POST https://stenobird.com/v1/public/podcasts/out-of-office-a-travel-podcast-629743/episodes/new-york-times-editor-stephen-hiltner-on-the-52-places-to-go-in-2026/transcription-requests` — Idempotently request low-priority transcript generation for this episode. - read_markdown: `GET https://stenobird.com/podcast/out-of-office-a-travel-podcast-629743/new-york-times-editor-stephen-hiltner-on-the-52-places-to-go-in-2026.md` — Read the agent-friendly Markdown representation of this episode resource. A page view does not enqueue transcription. Agents should invoke `request_transcript` explicitly when they need this episode processed. ## Transcript Full transcripts are not published on public pages unless there is a clear rights basis.