What This Series Is About ?

I've been learning Golang for a while now—but despite covering the basics multiple times, I still didn't feel confident enough to build a full application. At first, I thought I just wasn’t grasping the fundamentals properly. So I went back and revised the basics again. But even that didn’t give me the confidence I was looking for.

That’s when I realized the issue wasn’t with what I knew, but with how I was learning.

What worked for me in the past with other technologies was this: learning by doing. So I decided to take that same approach with Go. Instead of only reading or watching tutorials, I’ll build real applications, face real problems, and learn the concepts as I solve them. If you’re in the same boat—feeling stuck after learning the syntax but unsure how to apply it—this series is for you. Let’s walk this path together, learn practically, and gain confidence by building.

What to Expect ?

In this series, I’ll be building multiple small-to-medium apps using Golang. For each project, I’ll break down:

• What components it needs and why

• Why each component or library is chosen

• Component syntax, pros, and limitations

• How each part is implemented

I will discuss a detailed walkthrough of each decision—why a certain piece of code is written the way it is, what alternatives were considered, and how everything fits together. My goal is to provide a deeper understanding of not just how to build with Go, but why certain practices or patterns are followed. So when you encounter similar problems in the future, you’ll have the insight to adapt and solve them.

How to Follow the Series ?

Each topic/project in this series will be divided into three parts:

1. Understanding the Layer We’ll start by identifying the different layers in the app—like data, service, handler, etc.—and answer:

• What is the purpose of this layer?

• What role does it play in the app?

• Why do we need it?

2. Learning the Concepts Next, we’ll focus on the specific components or modules in Go:

• How do we implement them in Go?

• What tools or libraries are available?

• Why did we choose a specific tool or method?

3. Putting It All Together Finally, we’ll implement the component inside our project:

• Connecting the dots from concept to code

• Solving real problems using the ideas we’ve discussed

• Making sure we understand how and why it works

If you’re someone who learns better by building, not just reading, you’ll feel right at home. Let’s code, break things, fix them, and grow—together.