Tech lawyer Luis Villa returns to Go Time to school us once again on the intellectual property concerns of software creators in this crazy day we live in. This time around, we’re focusing on the implications of Large Language Models, code generation, and crazy stuff like that.

Who owns our code? Part 2

Your source for diverse discussions from around the Go community.  This show records LIVE every Tuesday at 3pm US Eastern. Join the Golang community and chat with us during the show in the #gotimefm channel of Gophers slack. Panelists include Mat Ryer, Jon Calhoun, Natalie Pistunovich, Johnny Boursiquot, Angelica Hill, Kris Brandow, and Ian Lopshire. We discuss cloud infrastructure, distributed systems, microservices, Kubernetes, Docker… oh and also Go! Some people search for GoTime or GoTimeFM and can’t find the show, so now the strings GoTime and GoTimeFM are in our description too.

Technology

Tech News

Podcasting

Gadgets

Software How-To

The 3 Musketeers return! Filippo Valsorda, Roland Shoemaker & Nicola Murino continue their deep-dive conversation with Natalie about Go’s crypto libraries. Also listen to Part 1 and Part 2!

What's new in Go's cryptography libraries: Part 3

In this episode, Ben Burkert & Chris Stolt join Johhny to explore the ups & downs of trying to get secure local development environments set up, why it’s hard & what you can do about it.

Local cert management for mere mortals

Natalie is joined by Carlos Becker (a Brazil-based software developer who maintains GoReleaser and other OSS software) to discuss how GOOS and GOARCH spark joy.

Ship software, not code

Felix Geisendörfer & Michael Knyszek join Natalie to discuss Go execution traces: why they’re awesome, common use cases, how they’ve gotten better of late & more.

The magic of a trace

In this episode Matt, Bill & Jon discuss various debugging techniques for use in both production and development. Bill explains why he doesn’t like his developers to use the debugger and how he prefers to only use techniques available in production. Matt expresses a few counterpoints based on his different experiences, and then the group goes over some techniques for debugging in production.

Who owns our code? Part 2

Download our free app to listen on your phone