Ade Mawan·4d agoThe Cost of Abstraction: When to Break SOLID Rules in High-Performance GoWe obsess over clean architecture — and pay the price in latency. Here is when to choose raw speed instead.
Ade Mawan·Oct 26The Developer’s Urgent Checklist for Recent PHP Vulnerabilities IN 2026Think your PHP stack is secure? These fresh 2026 exploits say otherwise — here is your emergency security checklist.
InLevel Up CodingbyAde Mawan·Aug 28When Clean Architecture Meets DDD: Where Do We Draw the Line?Clean Architecture and DDD explained together — finally clear, practical, and with real code examples.
Ade Mawan·Aug 27Stop Writing Code First: Why Great Engineers Start with a Failing TestThink TDD is just about testing? Think again. Here is how writing a failing test first actually builds bulletproof software design.
InLevel Up CodingbyAde Mawan·Aug 14I Tried 3 API Client Designs for Handling External API Calls in Go with Clean ArchitectureI tried 3 ways to structure external API calls in Go — only one of them survives Clean Architecture.A response icon3A response icon3
Ade Mawan·Aug 8I Tried Repository Pattern in Clean Architecture with Go — Here’s What I’d Do DifferentlyI implemented Repository Pattern in Go the wrong way first — here’s exactly what I’d change and why it matters.
Ade Mawan·Aug 4I Tried 3 ORMs in Go (and No ORM) — Here’s the Only One I’d RecommendI benchmarked GORM, ent, sqlx, and raw SQL in Go — here’s the ORM that actually earned my trust, and why.A response icon8A response icon8
Ade Mawan·Aug 3I Stopped Writing db: Tags in Go — Here’s What I Use Insteadsqlc generates type-safe Go code from your SQL queries — no struct tags, no manual scanning, no runtime mismatches.A response icon1A response icon1
Ade Mawan·Jul 30Interfaces Everywhere vs Interfaces Where Needed: A Go Architecture ExperimentA hands-on Go experiment comparing interfaces-everywhere against interfaces-where-needed — the results might change how you code.
Ade Mawan·Jul 2410 Mistakes I Stopped Making in My Go External Service LayerI made every mistake in Go’s external service layer so you do not have to — here is what I learned.A response icon2A response icon2