In-person July 2025 Meetup at Datadog

Welcome to our July 2025 Boston Go meetup at Datadog's Boston Office

We are looking for speakers for the next few months! Please reach out to us on Gophers Slack in #boston or via https://papercall.io/bostongolang to sign up to speak. It can be short or long, and it can be beginner, intermediate, or advanced--all talks are welcome! Some talk ideas to get your creativity flowing:

• An optimization you did at work
• How to use an open-source Go library
• A Go utility package you built as a side project
• Something new you learned about Go itself

And remember, the organizers are here to help you prepare. Whether that's idea formation, slide review, or rehearsing, we are here to help! Contact us at bostongolang@gmail.com if you need help with coming up with a talk idea or preparing or presenting your talk!

----------------------

Talks begin at 7, but doors open at 6:30, so attendees can socialize beforehand and enjoy complimentary snacks and drinks!

➤➤ Talks ➤➤

Title: Using Benchmarking and pprof to do performance analysis on Go
Speaker: Karl Meissner
Description: What happens when things are working well? Even more work!

The workload on a successful system is often scaled up, pushing a working system to the limits of capacity, and then the successful system starts to hit performance limits.

Before you pay to increase nodes in your cluster, use performance data to guide choices in performance changes to the Go code.

We look at two tools to measure Go performance.

• Benchmarking package - a library to run tests, similar to unit test that report performance numbers on functions.
• pprof - a runtime profiling package that measures CPU and resource usage.

Title: Building "git who" in Go
Speaker: Sinclair Target
Description: I recently built my first major project in Go, a CLI tool called “git who” that helps you explore who wrote what in a Git repository. It’s like a souped-up git blame.

There were a few interesting Go-specific things that came up as I was building this that I’d love to walk through.

• Walking the commit history of a repository using Go’s new iterators, and how to do error handling with iterators
• Error handling footguns I ran into using defer(), especially when managing the lifetime of a subprocess
• Using Go’s concurrency primitives to parallelize walking the commit history of a repository

➤➤ Important to Know ➤➤

Boston Golang officially adopts the Go Code of Conduct (https://golang.org/conduct). Harassment, bullying, and discrimination are unacceptable here, and if you witness or experience those or other harmful behaviors, please let the organizers know or email us at "bostongolang at gmail dot com"