Scoping in Go is built around the notion of code blocks. You can find several good explanations of how variable scoping work in Go on Google. I'd like to highlight one slightly unintuitive consequence of Go's block scoping if you're used to a language like Python, keeping in mind, this example does...
The use of context in Go can help you pass metadata through your program with helpful, related information about a call. Let's build an example where we set a context key, "stack", which keeps a history of the function names called over the lifetime of the context. As we pass the context object...
Go uses goroutines to execute multiple bits of code at the same time. Channels allow for the aggregation of the results of these concurrent calls after they have finished.
Say we need a map to store various versions of a configuration in Go. Here is a simple example of the structure:
Markdown is useful tool -- these blog posts are written in it. I like Markdown because once you learn it, it feels invisible. It is minimal and intuitive. However, sometimes you need it to do things a little differently.
Creating a Go module
supervisor is a UNIX utility to managing and respawning long running Python processes to ensure they are always running. Or according to its website: Supervisor is a client/server system that allows its users to monitor and control a number of processes on UNIX-like operating systems.
Querying S3 with Presto
Creating a Presto Cluster
Creating an Elixir module