This month, we are going to talk about code review and best practices in Go. The talk should have something in it for all levels from beginner to advanced Go developers. We’ll start out with an overview of why you should review code and what makes a good review. Then will move onto some specific examples of common things to look out for when reviewing Go. Topics covered will include: readability, logic, error handling, security, concurrency, and testing.

Speaker

Tyler Mann is co-founder and CTO at PullRequest, an Austin-based startup that provides code review as service through on-demand reviewers backed by automation. Before PullRequest, Tyler worked as a software engineer at Dropbox, Cisco, and other startups.

Sponsor

Food and drinks are sponsored by PullRequest — code review as a service that combines a network of on-demand reviewers with automation. PullRequest enables development teams to catch security threats, stop crashes, and fix performance issues before they reach production. PullRequest went through Y Combinator (S17) and is backed by investors, including Google's Gradient Ventures.

https://www.pullrequest.com

The space is provided by the Capital Factory.

Schedule

• 6:30-7:00 - Meet and greet, eat pizza, drink beer (responsibly!)
• 7:00-9:00 - Presentation and discussions

Location

We are located at the Capital Factory. We're in the same building as the Omni Hotel, but on the business side (Austin Centre). This month, we will be meeting in the room "Antone's" on the 16th floor.

Parking

Capital Factory offers validated parking for $7 if you park after 5pm and leave before 10pm. Details and other parking options are located here: https://www.capitalfactory.com/parking/

Accessibility

There is a step-free entrance to the building at the main Omni Hotel entrance located at 8th St. and San Jacinto Blvd (next to the valet stand).

Code of Conduct

We intend to maintain a friendly and welcoming environment for everyone attending. As such, we have adopted the Go Community Code of Conduct (https://golang.org/conduct). Please report any unwelcome behavior to the meetup organizers or to the Golang CoC Working Group (conduct@golang.org).