📰 Dev.to · Odilon HUGONNOT

Learning Go parallelism from scratch: goroutines, sync.WaitGroup, the classic loop closure trap and the race detector. With a concrete example — 10 URLs in 1s i

The concurrency vs parallelism distinction explained with a simple analogy, and how Go + Event Sourcing / CQRS leverage both: aggregate single-writer, fan-out p

How to design a 130-line Go package that guarantees err.Error() never leaks technical data into HTTP responses — safe by default, no discipline required.

PHP, Go, Python, JavaScript, Rust — no universal answer, but clear criteria. A pragmatic, opinionated guide for picking the right language for the job, with a q

The real resources, mental traps, conventions and a concrete learning path to learn Go when coming from PHP, Python or JavaScript.

How I built a complete automation service landing page — SEO, contact form, chatbox, modern design — in a single Claude Code conversation.

Hands-on report on fully automating article publishing: dev.to API, LinkedIn OAuth, image upload, and a unified Node.js script.

How I built ClaudeGate: an HTTP gateway in Go that wraps Claude Code CLI with an async job queue, SSE streaming, webhooks, and SQLite persistence — single stati

slog, errors.Join, context.WithoutCancel, iter.Seq2, testing/synctest, go tool — what has settled as standard in the best Go projects in 2025.

Three Go error patterns explained through a concrete ClaudeGate code review case. When to create a sentinel error, an error struct, or just use fmt.Errorf.

The Go "accept interfaces, return structs" convention explained through a concrete ClaudeGate code review case. When to apply it — and when leaving things as-is

Binance down for maintenance at 2am, your service keeps hammering it at 10 req/sec. Circuit breaker, exponential backoff retry, timeout, fallback: the complete

How to implement a per-IP rate limiter in Go using the token bucket from golang.org/x/time/rate: sync.Mutex, cleanup goroutine to prevent memory leaks, X-Forwar

The program has been running for 3 days. Memory is climbing slowly, requests are starting to slow...