• 0 Posts
  • 25 Comments
Joined 3 years ago
cake
Cake day: July 6th, 2021

help-circle
  • The name of the function, what goes in and what goes out in most cases should be enough to get a good idea on what the function does.

    It also helps to make a diagram of how everything ties together. Just boxes and arrows is enough.

    When writing your own code, it takes a bit of experience to know when to put something in its own function. It’s very obvious when you’re replicating code. It’s also very common to cut things up when a function gets too big. Look for bits of functionality that you can give a good name.


















  • I started a little over half a year ago with Go, coming from Python like the author. I definitely enjoy working in a strongly typed language and Go is usually quite fun to work with. This week I’m actually implementing a concurrency pattern for a ‘real’ problem, so eager to see how that works irl. I’ve yet to come across something where generics really make sense, but definitely curious to explore that with a real case as well.