In this post we'll learn about what are prototypes, why use them and how we can do inheritence with it.
Each year I post about what have I done in that particular year, inclining it more toward career. This is to document my process of learning over the year of 2020. I would say this was a productive year for people in IT. I myself completed some courses this year which would take more time if it was a non-corona year.
Like most of the self-taught programmers, I spent a lot of my years dabbling with different technologies. But there comes a time in every programmer's life when they have to learn data structures and algorithms to proceed in their careers. In this post I will go through the basics of data structures, what purpose they server and what's common between all of them.
Are you lost between Handle, HandleFunc, and HandlerFunc? If the answer is yes then this post is for you. To understand these pretty well we need to be familiar with interafces. Although `interface` is just a keyword, it's confusing at first when you are switching from Python like language; which does not have a similar keyword.
The way we used to deliver resources to the client in a server-client setup is now drifting away from REST to a more modern delivery mechanism. Two of them are gRPC and GraphQL. While both these solve a different kind of problem, REST is going to stay for a while. It is the simplest to learn at least.
If you think it’s slow, first prove it with a benchmark. Don't assume if things are slow. Benchmark it and see if they are really slow. Benchmarking is the way we check how fast our algorithm is for a given unit of the program. In benchmarking, we typically see how many iterations can a piece of code can run in a given time.
I am a self-taught programmer from start. And have limited knowledge of computer science. Which of course is changing day by day. I had a background in Python before getting into Go. So my recommendations will also be aligned with my experience level.
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.