Personal sharing
The article explains the Go 1.26 proposal introducing a standard Hasher[T] interface for custom hash and equality logic, outlines its definition, showcases practical examples, compares existing library approaches, and discusses the long‑term benefits and challenges for the Go ecosystem.
The Go 1.26 release extends the built‑in new function to accept expressions, allowing direct allocation of pointers with initial values, which reduces boilerplate, improves readability, and introduces a more consistent syntax for developers.
This article explores how a quirky snake game runs inside a browser’s address bar, the technical tricks behind it, and how recent security and API changes in modern browsers have turned such creative hacks into fragile experiments, highlighting the tension between innovation and safety.
The Go team repeatedly revisits error‑handling syntax, not to push new proposals immediately, but to reaffirm the language’s core philosophy of explicitness over implicitness, highlighting past failed attempts and the community’s cautious stance on balancing simplicity with clarity.
The author recounts fixing a complex Redis Vector Sets bug, explores how human creativity outperforms LLMs in devising efficient data‑consistency checks, and shares experimental ideas—including XOR accumulators and MurmurHash—to detect non‑mutual links in large HNSW graphs.
The article explains why Go 1.24’s SwissMap implementation may degrade performance for large, cold‑cache maps, describes the underlying structural reasons, shows real‑world impact on projects like Prometheus, and outlines the Go team’s planned fixes for Go 1.25.
This article examines Go’s concurrent mark‑sweep garbage collector, its latency advantages and scalability limits, then evaluates the new Green Tea GC proposal, detailing its span‑based scanning, benchmark results, and where it offers measurable improvements over the existing GC.
The article examines how AI coding assistants are reshaping software engineers' roles—from hands‑on creators to overseers—triggering an identity crisis, while exploring the loss of coding joy, emerging practices like prompt engineering, and strategies to adapt and retain core engineering craftsmanship.
The article argues that measuring developer productivity should focus on real business impact rather than individual output, using the story of Tim Mackinnon—an unproductive‑on‑paper programmer whose mentorship and team‑building skills dramatically boosted overall team performance.
gRPC offers high performance for microservices, but its generated protobuf code, required fields handling, and steep learning curve create ugly, hard‑to‑maintain implementations; this article examines those pain points, showcases examples, and suggests tools and best practices to mitigate them.
