Medium

syarif

Pinned

In

Level Up Coding

by

syarif

·

Jun 13, 2025

When Elegant Code Leads to Untraceable Bugs: A Case Study in Abstraction

The hidden cost of a beautiful design. A story of a bug that played hide-and-seek in our cleanest code.

When Elegant Code Leads to Untraceable Bugs: A Case Study in Abstraction

Pinned

syarif

·

Jun 4, 2025

The Illusion of Simplicity: What We Learned from Our Microservice Architecture

The Illusion of Simplicity: What We Learned from Our Microservice Architecture

Pinned

In

Level Up Coding

by

syarif

·

Jun 1, 2025

The Anti-Pattern That Cost Us Millions: Lessons from a Failed Project

How a seemingly innocuous design choice in our core infrastructure snowballed into cascading failures and a very expensive wake-up call for…

The Anti-Pattern That Cost Us Millions: Lessons from a Failed Project

syarif

·

1d ago

Go Isn’t Designed for DDD. We Use It That Way Anyway.

Domain-driven design assumes rich objects and inheritance. Go has neither. After 2 years forcing the match, here’s what we stopped…

Go Isn’t Designed for DDD. We Use It That Way Anyway.

In

Level Up Coding

by

syarif

·

3d ago

Go Value Objects Aren’t Verbose. They’re Bullet Armor.

When you stop using primitive strings for email, price, and userId — and start using Go types — an entire class of data corruption bugs…

Go Value Objects Aren’t Verbose. They’re Bullet Armor.

In

Level Up Coding

by

syarif

·

5d ago

Our Outbox Pattern Worked Until the Outbox Didn’t

The pattern that saves you from the dual-write problem has its own silent failure mode. We found ours 6 days after go-live, in a table…

Our Outbox Pattern Worked Until the Outbox Didn’t

In

Stackademic

by

syarif

·

5d ago

cgo Overhead Dropped 30%. When Should You Actually Care?

The headline sounds impressive. The reality is narrower: if your hot path doesn’t cross the Go-C boundary under load, the number doesn’t…

cgo Overhead Dropped 30%. When Should You Actually Care?

In

Stackademic

by

syarif

·

Jul 11

Weak Pointers Are in Go Now. Most Teams Shouldn’t Use Them.

The use cases are real but narrow. Outside cache invalidation and canonicalization, they add lifecycle complexity that will outlive the…

Weak Pointers Are in Go Now. Most Teams Shouldn’t Use Them.

In

Level Up Coding

by

syarif

·

Jul 10

The Go Error You See Is Never the Real Error

We wrapped errors, logged them, and monitored them. The one that mattered at 3AM was three layers below what our dashboards showed.

The Go Error You See Is Never the Real Error

In

Level Up Coding

by

syarif

·

Jul 8

Most Go Teams Are Still Using context.WithCancel Wrong

A deep dive into the 5 most common mistakes — and exactly how to fix them

Most Go Teams Are Still Using context.WithCancel Wrong

syarif

syarif

Backend Enthusiast | Golang Developer | Talk about software engineering, microservices, databases, and backend best practices.

Following

Help

Status

About

Careers

Press

Blog

Store

Privacy

Rules

Terms

Text to speech