PinnedYaninyz witty·16h ago5 coding habits I abandoned — And my code got betterThe practices I stopped following that made my code simpler and easier to maintain
PinnedYaninyz witty·1d agoStop waiting for production to expose these 10 Go mistakesThe bugs your tests, tooling, and code reviews should catch before users do
PinnedInCubedbyYaninyz witty·2d agoStop Managing Go configurations manually — Frameworks exists for a reasonWhen explicit configuration becomes more complicated than the tools you avoided
PinnedYaninyz witty·3d agoStop building Background Job systems in Go — You probably dont need oneWhen simple background tasks turn into unnecessary infrastructure
InCubedbyYaninyz witty·4d agoStop using the Result Type in Go — You’re solving the wrong problemWhy Go’s built-in error handling is often simpler than the abstractions replacing itA response icon1A response icon1
InDev GeniusbyYaninyz witty·5d agoStop using Interfaces everywhere in Go — You are making things worseThe hidden complexity of abstractions your code never neededA response icon3A response icon3
InDev GeniusbyYaninyz witty·6d ago10 Go tools you probably dont need — And what to use insteadThe popular tools quietly complicating your Go workflowA response icon2A response icon2
Yaninyz witty·Oct 287 Basic Go Concepts Even Experienced Developers get wrongThe fundamentals you think you’ve mastered — until production proves otherwiseA response icon1A response icon1
InDev GeniusbyYaninyz witty·Oct 27Stop using Worker Pools for everything in Go — Goroutines aren’t the problemYour worker pool might be hiding the bottleneck instead of fixing it
Yaninyz witty·Oct 26Your Go service isn’t idempotent — just because you added an idempotency keyThe hidden failure modes that make seemingly safe requests dangerous
