golang

golang

121 bookmarks
Custom sorting
Why Your Go Code Is Slower Than It Should Be: A Deep Dive Into Heap Allocations
Why Your Go Code Is Slower Than It Should Be: A Deep Dive Into Heap Allocations
Every Go developer eventually hits the same wall: your code works, but it's not fast enough. You've optimized your algorithms, removed unnecessary loops, and still—something's off. More often than not, the culprit is hiding in plain sight: excessive heap allocations. In this guide, I'll show you exactly how Go decides where to put your variables, why it matters for performance, and how to fix the most common allocation mistakes I've seen in production codebases. The Hidden Cost of Memory Allo
·cristiancurteanu.com·
Why Your Go Code Is Slower Than It Should Be: A Deep Dive Into Heap Allocations
Writing Better Go: Lessons from 10 Code Reviews
Writing Better Go: Lessons from 10 Code Reviews
Why do Go developers obsess over variable names, error handling, and interfaces, even when your approach does the job, too? Whether gently or not so gently, they'll remind you there's a right way to write Go. In this talk, I walk through frequent code review comments to show what looks like nitpicking is a window into Go's design philosophy. These aren't arbitrary style debates; they're about writing clear, deliberate, and unapologetically pragmatic Go. You leave with a better understanding of the "why" behind the rules and how embracing them can sharpen your code. GoLab 2025, Florence https://konradreiche.com/
·speakerdeck.com·
Writing Better Go: Lessons from 10 Code Reviews
Shipping an AI Agent that Lies to Production: Lessons Learned | Three Dots Labs blog
Shipping an AI Agent that Lies to Production: Lessons Learned | Three Dots Labs blog
The peak of hype isn’t the best moment to reflect on AI. Will it take your job, or is it the next fad like NFTs? Are AI startups ridiculously overvalued, or are the companies that sleep on AI doomed? Time will tell. LLMs are far from perfect, but I’m excited they’re here anyway. Not because of a silly promise to make me 10x more productive, but because they can solve some problems that were previously unsolvable.
·threedots.tech·
Shipping an AI Agent that Lies to Production: Lessons Learned | Three Dots Labs blog
Counter Service: How we rewrote it in Rust
Counter Service: How we rewrote it in Rust
The Integrity Data Platform team at Grab rewrote a QPS-heavy Golang microservice in Rust, achieving 70% infrastructure savings while maintaining similar performance. This initiative explored the ROI of adopting Rust for production services, balancing efficiency gains against challenges like Rust’s steep learning curve and the risks of rewriting legacy systems. The blog delves into the selection process, approach, pitfalls, and the ultimate business value of the rewrite.
·engineering.grab.com·
Counter Service: How we rewrote it in Rust