Josh Software

When developers first learn Go, goroutines feel almost magical. You write: One keyword, and your function runs concurrently. No complicated thread management, no heavy setup — just simple, elegant concurrency. But what happens when that goroutine never stops? In production, a downstream service might become unresponsive, a channel might stop receiving values, or a background … <...

@ybl to @oksbi: the hidden architecture, ownership, and lifecycle of India’s payment identity. Open Google Pay. Tap “Create UPI ID.” Wait two seconds. Done. You now have rahul@oksbi. Here’s what nobody tells you: Google didn’t create that. Google Pay doesn’t own it. And if Google Pay shut down tomorrow, what happens to your UPI ID …

How a brand-new, safe-but-body-carrying HTTP method finally fixes the awkward POST /search hack every backend developer has written at least once. Introduction Quick question: how many times have you built a POST /search endpoint that doesn’t actually change anything? If you’ve been writing backends for more than a year, the honest answer is probably “more …

Most Go developers know how to write efficient Go code. But very few know what happens to that code after go build. Consider: How many function calls happen here? The obvious answer is one. But the real answer may be zero. The Go compiler can inline add, turning the call conceptually into: It can then …