<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Google Calendar API on Subculture Science Research Group&#39;s Blog</title>
    <link>https://www.subcul-science.com/en/tags/google-calendar-api/</link>
    <description>Recent content in Google Calendar API on Subculture Science Research Group&#39;s Blog</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Sun, 15 Nov 2026 13:10:00 +0900</lastBuildDate>
    <atom:link href="https://www.subcul-science.com/en/tags/google-calendar-api/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Stop Calculating Business Trip Travel Time by Hand</title>
      <link>https://www.subcul-science.com/en/post/20261115booking-butler-solution/</link>
      <pubDate>Sun, 15 Nov 2026 13:10:00 +0900</pubDate>
      <guid>https://www.subcul-science.com/en/post/20261115booking-butler-solution/</guid>
      <description>Copying addresses into a map app and subtracting travel time from every meeting is a nightly ritual for anyone who travels for work. BookingButler derives the origin from the calendar and works backwards from arrival. Here is what got automated and what stayed manual.</description>
    </item>
    <item>
      <title>A Travel Calendar in Go, Gorilla Mux, and React: How BookingButler Is Built</title>
      <link>https://www.subcul-science.com/en/post/20261115booking-butler-tech/</link>
      <pubDate>Sun, 15 Nov 2026 13:00:00 +0900</pubDate>
      <guid>https://www.subcul-science.com/en/post/20261115booking-butler-tech/</guid>
      <description>How BookingButler turns Google Calendar events into departure times: a Go + Gorilla Mux API that exchanges the auth code, resolves stations with Google Maps, and fetches routes from NAVITIME. The design, the code, and the gaps left in it.</description>
    </item>
  </channel>
</rss>
