As I’ve been learning Go, I’ve knowingly put off picking up the concurrency model as I know it’s something I haven’t touched since college. Wanting an additional resource to dive back in, I’ve been reading Concurrency in Go by Katherine Cox-Buday. This book has been great as someone who generally understands the idioms of Go, but may not know where to start when it comes to concurrency.

The holidays are typically a great time to experiment, learn new things, and try to contribute back to your team. This year, I attempted to understand better how one of our command-line tools for Hipchat Data Center performs. While being feature complete, we wanted to better understand its resource consumption. Having heard so much about Go’s builtin performance tooling, I was excited to learn more and hopefully glean some valuable information to confirm assumptions and start brainstorming…

As of late, I have become increasingly interested in cryptography and network security. Having had a more frontend centric set of skills, many of these concerns were outside my scope. As I have worked more with web applications and the backends that power them, I have become more and more inquisitive about how we make these applications secure for consumers.