Farid Yusof's Blog

Early Feedback Loop

At most places I’ve worked before, we were conditioned to complete tasks entirely - PR, deploy to stage or testing environment - and only then would we get feedback from the “Product Team” / “QA” team.

I started becoming interested in computers when I was very young. Back then, I still remember using Windows 3.1. Although the main purpose was just to play Prince of Persia, I kept tinkering with other things too. Calculator, PaintBrush, and whatever I could explore.

As a kid, I really loved playing games. To the point where my parents would get angry because I was always gaming. At that time, my mother was still studying. She brought home books about computers, if I remember correctly, Borland C. I tried to implement the simple instructions from the book on the computer. By then, I was probably already using Windows 98.

You know, Go (or Golang, as some people call it) is known for its simplicity. But as your project grows, things won’t stay simple forever.

You can still maintain simplicity in your code organisation. How you structure your codebase really depends on your approach. Some developers start encapsulating things immediately, while others prefer to keep it simple at first.

When you start structuring your codebase, you might be biased-especially if you’re coming from a different ecosystem or programming “tribe.” Your structures are probably influenced by those other languages.