Why I'm Learning Go in 2026 (A Java/Kotlin/Rust Engineer's Take)
I've spent the better part of six years writing Java and Kotlin in production — FinTech systems, logistics platforms, EdTech backends. Somewhere in the last year I also went deep on Rust, building an AI gateway and a RAG server from scratch. So the obvious question is: why pick up another language?
Short answer: because every team I want to work for in 2026 is either already running Go in production, or wishes they were.
This post kicks off a series where I document learning Go properly — not "hello world and a for loop" learning, but the kind that ends with a real, production-grade service. If you're a backend engineer coming from the JVM world (or from Rust, or anywhere else) and curious whether Go is worth the detour, this series is for you.
The Itch That Started This
