
In-loop defer costs 90% of your memory, and other Go war stories
The pick of the writing today is a profiling walkthrough showing how a defer sitting inside a hot loop quietly ate 90% of a service's memory until someone went in with pprof and hoisted it out. It pairs well with a post on why a 1B-parameter Ollama model made a poor trading risk gate for a handful of small Go jobs placing real orders, which is the kind of lesson you would rather read than learn firsthand. Elsewhere there is a guide to building a typed, stateless MCP server with OAuth 2.0, and a field report on a shared Go platform library where every gRPC server introspects its own migrations and config without hand-written glue.

The pick of the writing today is a profiling walkthrough showing how a defer sitting inside a hot loop quietly ate 90% of a service's memory until someone went in with pprof and hoisted it out. It pairs well with a post on why a 1B-parameter Ollama model made a poor trading risk gate for a handful of small Go jobs placing real orders, which is the kind of lesson you would rather read than learn firsthand. Elsewhere there is a guide to building a typed, stateless MCP server with OAuth 2.0, and a field report on a shared Go platform library where every gRPC server introspects its own migrations and config without hand-written glue.

I have a few small Go jobs that place orders on my own Zerodha account. They already talk to a language model for advice, and in September… Continue reading on Medium »
You know, sometimes building software feels a lot like playing a never-ending game of “Whack-A-Mole,” right? Especially when it comes to… Continue reading on Medium »
Story of how go profiling and simple defer tricks can help you reduce memory footprint for massive customer inputs Continue reading on Stackademic »
A JSON file you can read with your eyes and a SQLite database you can put real data in, behind the same interface and kept honest by one… Continue reading on Medium »
One Go app, three data layers, and a 500 that should have been a 404. Continue reading on Medium »
Can TypeScript beat Rust and Go? Bun enters a one-million-call Fibonacci battle. Pick your winner before the clock starts. Median ...
You think your Node.js services handle many tasks at once, but one large JSON payload can freeze every other request while Go ...
Write typed Go functions, return two values at once, and learn why Go handles errors with if err != nil instead of try/catch. Watch the ...
Same massive JSON payload, but in Go the waiter asks a busboy to fold the napkins and the timeout errors disappear. Check out ...
Mutex or channel? Most Go devs pick the wrong one. The rule: guarding shared state → mutex. Moving data between goroutines ...
PWA dashboard for monitoring OpenWrt/GL.iNet home networks: fleet status, per-router health, devices, WireGuard peers, AdGuard Home stats and alerts in real time (SSE). Go backend + React 19 frontend,


Co-authored-by: osauer

