Whether you hate SQL or merely tolerate it, you probably use it in your application. We'll look at ways to cleanly organize your SQL code in Go.| Go Beyond
Go's lack of frameworks means you need to bring your own design. We'll walkthrough a common, reusable design pattern for create/read/update/delete in Go.| Go Beyond
Despite such a simple language, Go developers have found a surprising number of ways to create and use objects. In this post we’ll look at a 3-step approach to object management—instantiation, initialization, & initiation. We’ll also contrast this with other methodologies for creating and| Go Beyond
Go’s paradox is that error handling is core to the language yet the language doesn’t prescribe how to handle errors. Community efforts have been made to improve and standardize error handling but many miss the centrality of errors within our application’s domain. That is,| Go Beyond
For me, the hardest part of learning Go was in structuring my application. Prior to Go, I was working on a Rails application and Rails makes you structure your application in a certain way. “Convention over configuration” is their motto. But Go doesn’t prescribe any particular project layout or| Go Beyond
Vendoring. Generics. These are seen as big issues in the Go community but there’s another issue that’s rarely mentioned — application package layout. Every Go application I’ve ever worked on appears to have a different answer to the question, how should I organize my code? Some applications push| Go Beyond