Umar Farooq (@0xffff_umar) 's Twitter Profile
Umar Farooq

@0xffff_umar

Backend Engineer @demystdata

ID: 2810612815

calendar_today15-09-2014 03:31:05

2,2K Tweet

191 Followers

692 Following

Zigtur (@zigtur) 's Twitter Profile Photo

Mayowa Olatunji Obviously, I would stop looking for the “best resources” (which I see as procrastination) and start working. You’ll learn as you go. Solana codebase? Use Solana, Anchor and Rust docs. Cosmos SDK codebase? Use Cosmos and Golang docs.

The Go Dev (@thegodev) 's Twitter Profile Photo

Explore Go resource pooling patterns to reuse connections, avoid memory spikes, manage lifecycles and ensure steady performance #DEVCommunity #GoLang dev.to/leapcell/the-a…

Golang News & Libs & Jobs - human 🗣️ , no 🤖 (@golangch) 's Twitter Profile Photo

A feature complete, pure Go library for interacting with #Kafka from 0.8.0 through 4.0+. Producing, consuming, transacting, administrating, etc. #golang github.com/twmb/franz-go

A feature complete, pure Go library for interacting with #Kafka from 0.8.0 through 4.0+. Producing, consuming, transacting, administrating, etc.
#golang

github.com/twmb/franz-go
Ashutosh Maheshwari (@asmah2107) 's Twitter Profile Photo

You've built your first microservice. Service A needs to call Service B. How does it know where Service B is? Simple. "Just put Service B's IP address in Service A's configuration file." but this is one of the most common and brittle design choice...🧵

GoLang Trends (@golangtrends) 's Twitter Profile Photo

Clean Architecture in Go: A Practical Guide with go-clean-arch #golang #dormosheio #webdev #programming #backend dormoshe.io/trending-news/…

Paul (@nilotpaul_n) 's Twitter Profile Photo

You’ve Been Writing HTTP Handlers Wrong Most Go devs write handlers that don’t return errors (standard way), they just log or http.Error inline. But it’s cleaner to let handlers return errors and handle them centrally. This makes your code more testable, readable, and

You’ve Been Writing HTTP Handlers Wrong

Most Go devs write handlers that don’t return errors (standard way), they just log or http.Error inline. But it’s cleaner to let handlers return errors and handle them centrally. This makes your code more testable, readable, and
Independent Urdu (@indyurdu) 's Twitter Profile Photo

اسلام آباد کے شہریوں کا 50 سال پرانی سٹیشنری کی دکان کو شمعیں جلا کر خیر باد

GoLang Trends (@golangtrends) 's Twitter Profile Photo

Go's slog: Modern Structured Logging Made Easy #golang #dormosheio #webdev #programming #backend dormoshe.io/trending-news/…

Akhilesh Mishra (@livingdevops) 's Twitter Profile Photo

Kubernetes is beautiful. Every Concept Has a Story, you just don't know it yet. In k8s, you run your app as a pod. It runs your container. Then it crashes, and nobody restarts it. It is just gone. So you use a Deployment. One pod dies and another comes back. You want 3 running,