There is another option to use optional parameter which we saw in last post. We use something called option struct. Much similar to what we do in JavaScript. Without further ado, let's get started.

In Python we can set some parameters to default by doing option=True. But in Go we don't have that. In Go we do things differently. In Go we compose one function out of multiple helper functions. In this post we are going to explore the world of variadic function.

Sending a POST request in Go is not an easy cake. One need to structure every piece of data being send. Today I'm gonna show how you can make a little easier.

There are two options, either you put version info in code and then use that in automation to create git tag. The another way is to let git tag drive the version info in the compiled application. In this post we see the later option.

In simple words, WASM let's us use code in browser, which is written in other language. The twist here is, that language does not have to be JavaScript or Node. It could be languages such as Python or Go. Today we see how we write code in Go to run that in browser environment.

Docker makes it easy to develop and deploy application, reducing friction between the processes. And ElasticBeanstak is a great platform build upon EC2 infrastructure which provides provisioning capability without much effort.

Some of the features of BoltDB is... It's ability to do concurrent reads. It's nature of being Go native, which means it can compile where Go can compile. Read more about it in the post.

In this post, I talk about why TDD is important. Why it is essential part of build process. I also talk a little bit about test coverage and having more coverage is always better. I also provision a Travis CI pipeline to test same application in different environments.

One of the benefits of multi stage build is that you can improve on build time. Second benefit is that size of your final images can drastically reduced.

This year was a transition period for me from a career perspective. I was hearing, understanding and practicing stuff like microservices, fault tolerance, cross-site deployment, REST APIs, software deployment system, agile development and attending meetings & training sessions with the people on the other side of the planet.

Earlier on, I was decided on to giving my website a go backend, but I later thought it was an overkill to use golang as a backend for a personal website and I should keep that enthusiasm for a real app. But for now, I'll use a static site generator called Hugo for blogging.

Why wait for CI/CD services to run your test? And in case you've already submitted a pull request, you'll have to push another commit to fix the cause of failed test held by CI provider. You can prevent that by running unit tests locally before every commit.

We'll see how we can create better renders and how render times can be reduced by merely changing some factory settings, and also what prices we might have to pay for that optimization.