I just got back home recently from Seattle after attending GopherCon 2026. Just like in 2023, I had a great time yet again. I always come back feeling inspired after seeing all the amazing things happening in the Go community. I figured I write up a little recap this time to help reflect on what all went down. Also maybe this post might give someone an idea on what to expect if they’ve never been 🤷🏽‍♂️.

I run a fantasy football league on things get pretty heated during the season. Debates and trash talks go on daily in our GroupMe chat and the guys like to remind each other about their resume. How many wins they have, how many championships, how many times someone beat someone else, you name it. Ideally these status would be easy to check on our ESPN fantasy app, but ESPN’s platform has some shortcomings here.

Ever since agents made it into the mainstream, I’ve been really interested in how they work. I’ve always wanted my own personal Jarvis, and now I feel like I have the chance to build one myself. At its score, it’s mechanics: a loop that observes input, decides what to do, acts, and repeats. At scale, things get much more complex, especially for user-facing products like ChatGPT or other AI coding assistants. What lies in between is a lot of lessons, techniques, and mechanics.

Ok, so let’s say you have an HTTP client where you need to get information from the request and response calls for logging or debugging reasons. One way to do this is to create a custom RoundTripper to handle said logging.

What is a RoundTripper?

A RoundTripper is an interface that implements the RoundTrip function which makes the HTTP request and response on behalf of the http.Client, within the client’s Do() function. There is a field on the client called Transport that holds the implementation. Go will use the default version if no custom RoundTripper is provided.