# Gophers Say! GopherCon EU Berlin 2024

Page: https://stenobird.com/podcast/go-time-golang-software-engineering/gophers-say-gophercon-eu-berlin-2024
Text version: https://stenobird.com/podcast/go-time-golang-software-engineering/gophers-say-gophercon-eu-berlin-2024.md
Podcast: [Go Time: Golang, Software Engineering](https://stenobird.com/podcast/go-time-golang-software-engineering)
Published: 2024-06-25T17:30:00+00:00
Episode link: https://changelog.com/gotime/320
Audio file: https://op3.dev/e/https://cdn.changelog.com/uploads/gotime/320/go-time-320.mp3
Processing state: processed
JSON: https://stenobird.com/v1/public/podcasts/go-time-golang-software-engineering/episodes/gophers-say-gophercon-eu-berlin-2024
Duration seconds: 2460

## Resource

A live recording of the 'Gopher Say!' game show from GopherCon EU Berlin 2024. The episode features a technical deep dive into automated SDK generation followed by a high-energy audience survey game.

## Highlights
- Main idea: Automating SDK maintenance using OpenAPI specifications reduces manual overhead in growing teams
- Practical takeaway: Use frameworks like Goa or Schema to ensure APIs are documented and machine-readable from the start
- Practical takeaway: Integrate spec generation into CI/CD pipelines to trigger automated pull requests for breaking changes
- Failure mode: Relying on manual SDK updates leads to drift and maintenance bottlenecks as API complexity increases
- Main idea: The 'human in the loop' is still essential to validate that generated SDKs meet ergonomic and documentation standards

## Topics

Go Programming, OpenAPI, SDK Generation, Software Engineering, API Development, CI/CD, GopherCon Europe, Developer Productivity

## Chapters
- 1:00 — Automating SDK Generation: A deep dive into using OpenAPI specs and Speakeasy to automate the end-to-end workflow of generating and maintaining SDKs in multiple languages.
- 7:45 — Gopher Say! Game Show Begins: The live audience game show kicks off at GopherCon EU Berlin, featuring competitive guessing based on developer survey results.
- 1:44 — The Debugging Debate: Contestants guess common developer debugging tools, debating the merits of print statements versus structured logging.
- 2:13 — Developer Fuel Survey: A look at what developers drink while coding, covering everything from coffee and tea to water and soda.
- 2:51 — Go Language Keywords: The game tests knowledge of Go syntax, specifically focusing on the most common keywords that come to mind for developers.
- 3:25 — Essential Coding Dependencies: The final round explores what developers claim they cannot code without, ranging from computers and Vim to music and even cats.

## Actions

- request_transcript: `POST https://stenobird.com/v1/public/podcasts/go-time-golang-software-engineering/episodes/gophers-say-gophercon-eu-berlin-2024/transcription-requests` — Idempotently request low-priority transcript generation for this episode.
- read_markdown: `GET https://stenobird.com/podcast/go-time-golang-software-engineering/gophers-say-gophercon-eu-berlin-2024.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.