Topic
3 articles found
In 2017 I was maintaining a Node.js ecommerce server when a new project landed on my desk — an IoT platform for vehicle tracking devices. Thousands of devices, transmitting data continuously, with clients expecting real-time visibility into what the devices were reporting. The Node.js server started
I had three repositories that looked identical. UserRepository, ProductRepository, OrderRepository: same structure, same FindByID, same List, same pagination logic. The only difference was the return type. Three copies of the same code. When Go 1.18 shipped with generics, I wanted to merge them all.
Today I learned something simple, but it changes how “professional” your Go project feels. It’s about this line: go mod init github.com/yourname/module-name vs go mod init module-name At first, it feels like just naming. But in Go, this is actually your project identity. When you use: github.com/you