Go Time: Golang, Software Engineering

The bits of Go we avoid (and why)

This will blow your docs off

What's new in Go 1.20

Is htmx the way to Go?

How to ace that CFP

Long-term code maintenance

Who owns our code? Part 2

How Go helped save HealthCare.gov ♻️

A special New Year's fireside chat

Making Go more efficient

Hacking with Go: Part 3

To TDD or not to TDD

How Pinterest delivers software at scale

gRPC & protocol buffers

Debugging Go

Go in medicine & biology

Spooky stories to scare devs 👻

Who owns our code?

Hacking with Go: Part 2

Mat's GopherCon EU diary

Functional programming with generics?

Engineering interview tips & tricks

Stay agile out there

Avoiding bloat

Inside GopherCon

The art of the PR: Part 2

The art of the PR: Part 1

The pain of dependency management

Gophers Say! GopherCon EU Edition

What's new in Go 1.19

Go for beginners ♻️

Might Go actually be OOP?

Go tooling ♻️

Thoughts on velocity

2053: A Go Odyssey

Observability in the wild: strategies that work

Going through the news

The myth of incremental progress

Berlin's transition to Go

Revisiting Caddy

What to do when projects get big and messy

Go and PHP sitting in a tree...

Analyzing static analysis

Instrumentation for gophers

Go code organization best practices

Answering questions for the Go-curious

How can we prevent legacy from creeping in?

Making the command line glamorous

Mastering Go

Bob Logblaw Log Blog

Why immutable databases?

Going with GraphQL

The *other* features in Go 1.18

Building and using APIs with Go

MLOps in Go

Migrations without migraines

AI-driven development in Go

Go beyond work

Gophers Say! GopherCon Edition

The funny bits from 2021

Mat asks the Go Team anything

Coding Go in the blind

Our first decade with Go

Maintenance in the open

Eventually consistent (managing data at scale)

Hacking with Go: Part 1

Discussing Go's annual developer survey

Just about managing

Maintaining ourselves

eBPF and Go

Gophers Say What!?

Go on hardware: TinyGo in the wild

The little known team that keeps Go going

Books that teach Go

Building actually maintainable software

To build, or to buy, that is the question

Don't forget about memory management

Caddy V2

Data streaming and Benthos

Opening up the opinion box

How to make mistakes in Go

Do devs need a product manager?

SIV and the V2+ issue

Fuzzing in the standard library

Pop quiz time! 😱

Giving TDD a Go

All about Porter

Using Go in unusual ways

Go Battlesnake Go!

Building for Ethereum in Go

Are frameworks getting an Encore?

Event-driven systems

What makes wonderful workshops?

Building startups with Go


The ultimate guide to crafting your GopherCon proposal

Trials and tribulations of testing in Go

Releasing with (and without) GoReleaser

Design philosophy


Talkin' 'bout code generation

Go at Clever

Indecent (language) Proposals: Part 2

The art of reading the docs

Indecent (language) Proposals: Part 1

When Go programs end

Why writing is important

CUE: Configuration superpowers for everyone

We're talkin' CI/CD

Go Panic!

Go in other spoken languages

What to expect when you’re NOT expecting

The engineer who changed the game

Play with Go

The secret life of gophers

When distributed systems Go wrong

What would you remove from Go?

How Go helped save HealthCare.gov

GitHub's Go-powered CLI


Introducing your team to Go

Cloud Native Go

There's a lot to learn about teaching Go

The one with Brad Fitzpatrick

Community Q&A

Hits of the Summer


Building desktop apps with Go + web tech


All about that infra(structure)


The latest on Generics

The future of Testify

Your first week with Go

Focusing in on PostgreSQL

Go in production at Pace.dev

We have regrets


Reflection and meta programming

The trouble with databases

On community and safety

Challenges of distributed messaging systems

Black Hat Go

Immediate mode GUIs

WebRTC in Go

The monolith vs microservices debate

Organizing for the community

Enterprise Go?


The Zen of Go

It is Go Time!

Pow! Pow! Power tools!

On the verge of new AI possibilities

Stop the presses

Quack like a wha-?

Telemetry and the art of measuring what matters

Unusual uses for Go: GUIs

Grokking Go.dev

Cloudy with a chance of Kelsey Hightower

Go at Heroku

Go at Cloudflare

defer GoTime()

Bugs are in the air

The fireside edition 🔥

Concurrency, parallelism, and async design

Graph databases

Compilers and interpreters

Code editors and language servers

Kubernetes and Cloud Native

Building search tools in Go

All about caching

On application design

Security for Gophers

Creating the Go programming language

Hiring and nurturing junior developers

Generics in Go

LIVE from Gophercon UK

Serverless and Go

The infrastructure effect: COBOL and Go

The importance of representation

Structuring your Go apps

If you've never been to GopherCon...

Go is eating the world of software

Web development in Go

if err != nil

Go tooling

The art of execution

Go 💚 open source

Functional programming?

Go modules and the Athens project

Go for beginners

Hardware hacking with TinyGo and Gopherbot

It's time to talk about testing

Hiring and job interviews

All about APIs!

Go 2 and the future of Go

New Go branding strategy

Hacking drones with Go

BONUS – Go and WebAssembly (Wasm)

Dependencies and the future of Go

Building a distributed index with Go

GoLand IDE and managing Gopher Slack

Gophercises and creating content for Gophers

CockroachDB and distributed databases in Go

Learning and teaching Go

Go is for everyone

From Russia with love

Golang Flow, FaaS, and Buffalo

SPECIAL — Ask us anything! (pt. 2)

Supporting the Go community

Performance, fuzzing & magic

GopherCon Brazil & Genetics

InfluxDB & IoT Data

Changelog Takeover — K8s and Virtual Kubelet

Building Blocks

Loggregator, gRPC, Diodes

Why WADL When You Can Swagger?

Improved Improved Improved (i3)

Full-time Open Source

Presenting a Pragmatic Perspective

Container Security and Demystifying Complexity

Dep, Cross-platform, and Getting Started

Go at Walmart (and Scale)

GopherCon 2017: A Retrospective

All About The Go Compiler

Infosec research and app security

Bringing Kubernetes to Azure

Adventures in VS Code

Restic and backups (done right)

Docker, Moby, Containers

Periph.io, Drivers, Hardware

SPECIAL — Ask Us Anything!

Go4 and Contributing to Go

Getting Better, Mentoring, Drawing Gophers

Race detection, firmware, production-grade Go

Distributed Messaging and Network Clients

Game Development and Rebuilding Microservices

Splice, Audio, Compassion

Go Developer Survey

Gobot, Hardware, Gatekeeping

Dependency Management, Semver, Community Consensus

Honeycomb, Complex Systems, Saving Sanity

Pachyderm, Provenance, Data Lakes

Gopherize.me, GitHub Stars, BitBar

Hellogopher, whosthere?

Go, Jocko, Kafka

Discussing Imposter Syndrome

Go and Buffalo Live from Dunkin' Donuts

Creating a programming language

The Go Compiler and Go 1.8

Teaching and Learning Go

Go Kit, Dependency Management, Microservices

Juju, Jujucharms, Gorram

Open Sourcing Chain's Developer Platform

Go work groups and hardware projects

Building a startup on Go

Kubernetes, Containers, Go

Programming Practices, Exercism, Open Source

Go in 5 Minutes & design patterns

Monorepos, Mentoring, Testing

SOLID Go Design

The Go Standard Library

Matt Holt on CaddyServer, the ACME Protocol, TLS

Francesc Campoy on GopherCon and understanding nil

Beyang Liu on Go at Sourcegraph and Writing Better Code

Jessie Frazelle on Maintaining Open Source, Docker, dotfiles

State of Go Survey and Go at Heroku

Scott Mansfield on Go at Netflix

Asim Aslam on Micro, the Go Microservice Toolkit

Raphaël Simon on goa, the Framework for Building Microservices

Bill Kennedy on Mechanical Sympathy

Sarah Adams on Test2Doc and Women Who Go

Go and Data Science

Early Go Adoption

Go Community Discussions

It's Go Time!