DEVELOPER NEWS STREAM
Direct logs, engine updates, and framework notifications parsed from curated RSS feeds and announcements, updated hourly.
AbhiudayObservation Haki for Manga: Why I Built a Change Data Capture (CDC) Pipeline Just to Read Manga
Observation Haki for Manga: Why I Built a Change Data Capture (CDC) Pipeline Just to Read...
ArthurGemma 4 E4B caught three planted fabrications in 50 seconds — on a laptop, no cloud
This is a submission for the Gemma 4 Challenge: Build with Gemma 4 What I...
Michael G. JacksonDiscover Japanese Pokémon Booster Boxes
Experience the thrill of opening TCG Pokémon booster boxes imported from Japan. These boosters offer exclusive cards that can enhance your collection
Atila TairI Ran a Honeypot for a Week. The Results Were Shocking.
I put a deliberately vulnerable-looking honeypot on a small cloud VPS and left it exposed to the...
Eduard MaghakyanI got tired of clicking through the Stripe dashboard, so I built a CLI
Stripe products and prices belong in version control. Here's the YAML-first workflow I wanted, and the CLI I wrote to get it.
Gabriel AnhaiaFunctional Core, Imperative Shell in Go: Where Side Effects Belong
Pure pricing in the middle, dirty I/O at the edges. The Go split that makes domain tests run in microseconds and integration tests rare.
Gabriel AnhaiaThe Dependency Rule, Written as a CI Check in Go
Stop trusting code review to enforce hexagonal boundaries. Three ways to fail the build when domain imports infra.
Gabriel AnhaiaDomain Model vs Persistence Model: The Mapper Layer in Go
One Order aggregate with behaviour, one OrderRow flat enough to scan into. The mapper between them is what keeps the seam honest.
Gabriel AnhaiaAggregate Identity in Go: UUID v7, ULID, or Snowflake?
Picking the right ID for your DDD aggregate roots in Go. UUID v4, v7, ULID, Snowflake — sortability, distribution, B-tree friendliness, decision rule.
Gabriel AnhaiaSaga Orchestration in Go: A State Machine for Multi-Service Workflows
Make a multi-service order flow survive crashes. A Go state machine, compensation per step, idempotency keys, and Postgres-backed resumes.
Gabriel AnhaiaSpecifications in Go: Composable Query Predicates Without an ORM Leak
Predicate objects you can AND, OR, and NOT in domain terms — translated to SQL at the edge. The Specification pattern, in idiomatic Go.
Gabriel AnhaiaErrors as Domain Concepts: Typed Errors That Carry Meaning in Go
Domain errors deserve their own types. Infra errors stop at the adapter. Here is the pattern that keeps your Go domain honest.
Gabriel AnhaiaThe Anti-Corruption Layer for a Legacy Database You Cannot Replace
You inherited a 2003 ERP schema with tflag1, dt_cre, and customer_v2. An ACL adapter keeps your fresh Go domain clean while the old DB stays put.
Gabriel AnhaiaApplication Service vs Domain Service in Go: Two Layers, Different Jobs
Two layers, two jobs. Application services orchestrate use cases; domain services hold cross-aggregate rules. Mixing them is where Go hex services rot.
Gabriel AnhaiaType-Driven Domain Design in Go: Encoding Invariants at Compile Time
Make invalid states unrepresentable. Three Go patterns that turn runtime bugs into compile errors: parse-don't-validate, states-as-types, phantom types.
Gabriel AnhaiaEvent Sourcing in Go: An Append-Only Store and a 200-Line Replay
Events are the source of truth, current state is a fold over events. The whole pattern fits in 200 lines of Go — append, replay, snapshot.