Answering questions or helping other people seems to be a good way for me to learn more about a language. I’ve been trying to be more active on the Go forums for this reason, answering questions as they pop up (especially focusing on the ones that may not have gotten much attention). Even a very simple question can get you to go down a rabbit hole and learn more as you’re formulating an explanation as part of the answer.

Answering questions or helping other people seems to be a good way for me to learn more about a language. I’ve been trying to be more active on the Go forums for this reason, answering questions as they pop up (especially focusing on the ones that may not have gotten much attention). Even a very simple question can get you to go down a rabbit hole and learn more as you’re formulating an explanation as part of the answer.

When I want to do some rough timing comparisons or get a quick idea of what part of Thing X is taking so long I sometimes just time a few functions. I used to do this by getting st := time.Now() at the beginning of the function and then time.Since(st) at the end. It recently hit me that the same thing could be achieved with less duplication and messiness to clean up (when removing the timings) with something like this:

When I want to do some rough timing comparisons or get a quick idea of what part of Thing X is taking so long I sometimes just time a few functions. I used to do this by getting st := time.Now() at the beginning of the function and then time.Since(st) at the end. It recently hit me that the same thing could be achieved with less duplication and messiness to clean up (when removing the timings) with something like this:

When you’re helping coordinate a workflow switch between half a dozen different studios, making sure all tools support new workflow, and shipping at the same time: