Lenon Rodrigues·Mar 10Go Tip #8: Stop Using Mutex for Everything, The Confinement PatternOne of the most common mistakes when writing concurrent code in Go is this:
Lenon Rodrigues·Mar 4Kafka Rebalancing Explained (Part 1): Eager vs CooperativeThis article is Part 1 of a short series on Kafka rebalancing in production.A response icon1A response icon1
Lenon Rodrigues·Oct 12, 2025Go Tip #7: Receivers in Go, Pointer vs Value (the 80/20 you’ll actually use)In day-to-day Go, choosing between pointer (*T) and value (T) receivers is where correctness, performance, and API clarity quietly live or…
Lenon Rodrigues·Oct 14, 2024Go Tip #6: Using Generics for Better Type Safety in GoIn modern Go, generics offer a way to improve type safety while maintaining flexibility. This article walks you through an example of using…
Lenon Rodrigues·Oct 9, 2024Go Tip #4: Handling and Returning Errors GracefullyIn Go, error handling is an essential part of writing robust and reliable applications. Instead of relying on exceptions or error codes, Go…
Lenon Rodrigues·Oct 7, 2024Data Transfer in Apache Flink: A Comprehensive OverviewIn distributed stream processing frameworks like Apache Flink, efficient data transfer between different components is crucial to…A response icon1A response icon1
Lenon Rodrigues·Oct 7, 2024Go Tip #3: Concurrency — Share by CommunicatingConcurrency is a broad topic, but Go offers a unique perspective on how to approach it. In many languages, concurrent programming requires…
Lenon Rodrigues·Oct 5, 2024Go Tip #2: Using defer for Resource ManagementIn Go, the defer statement provides a powerful way to manage resources and ensure certain actions are performed when a function is about to…
Lenon Rodrigues·Sep 30, 2024Go Tip #1: Memory Allocation with newWhen working with Go, you’ll come across two essential functions for memory allocation: new and make. While they might seem similar at…