If you'd like to check the code, the PR is still active.

StaticBackend repo: https://github.com/staticbackendhq/core

My course on Building SaaS in go

Share episode topic idea with me on Twitter @dominicstpierre

We go over what are pointers and when to use or not use them. For instance, this is probably not a good use for pointers.

func main() {
  var i int = 10
  abc(&i)
}

func abc(i *int) {
  *i = 15
}

In my opinion any dereferencing is probably bad. Better way:

func main() {
  var i int = 10
  i = abc(i)
}

func abc(i int) int {
  return 15
}

I also try to give some basics info regarding the stack and heap and why pointers might not be seen as an optimization.

I have a course on building SaaS in Go.

Follow me on Twitter.

Don't stress too much about having the "proper" project structure to the point where you might over-engineer or be paralyzed by the thought of doing something wrong.

It's just hard, and even 5+ years of Go experience will not ensure you're creating the optimal packages and structure. It's an art mixed with preferences that become a little easier with time but remain challenging.

I wrote a getting started with Go guide that cover a little about project structure and how to get started with Go.

If you're in writing web applications and maybe even SaaS, I have a course on creating API-first SaaS with Go.

• Wrapping error: fmt.Errorf("error trying to do X: %w", err)
• Package errors: https://pkg.go.dev/errors

Example of not using the happy path at 1st indentation:

An   example of happy path in idiomatic Go:

if !somethingElse() {
  // handle something else false
}
// Happy path

My course on building SaaS apps in Go.