Corentin GS
@corentings.dev
Teaching Go for cloud-native microservices to backend beginners. Self-taught developer with 5 years of experience. Making the practical course I wish existed.
Read this and more on my Typeshare Social Blog: https://typeshare.co/corentings/posts/context-gos-elegant-weapon-against-concurrency-chaos-f0amr
Context: Go's Elegant Weapon Against Concurrency Chaos
In the wild west of concurrent programming, Go's context package emerges as the sheriff that brings
typeshare.co
June 4, 2025 at 8:00 AM
Read this and more on my Typeshare Social Blog: https://typeshare.co/corentings/posts/context-gos-elegant-weapon-against-concurrency-chaos-f0amr
Read this and more on my Typeshare Social Blog: https://typeshare.co/corentings/posts/context-leaks-the-invisible-technical-debt-draining-your-go-systems-5065t
Context Leaks: The Invisible Technical Debt Draining Your Go Systems
In Go, context leaks are silent killers.They don't raise alarms. They don’t crash your app on day on
typeshare.co
June 2, 2025 at 7:00 PM
Read this and more on my Typeshare Social Blog: https://typeshare.co/corentings/posts/context-leaks-the-invisible-technical-debt-draining-your-go-systems-5065t
But if you're building microservices, backend APIs, or distributed systems, Go or even C# tends to be a better choice. Simpler tooling, faster development, easier onboarding.
It's not about switching — it's about picking the right tool for the job.
It's not about switching — it's about picking the right tool for the job.
May 29, 2025 at 5:35 PM
But if you're building microservices, backend APIs, or distributed systems, Go or even C# tends to be a better choice. Simpler tooling, faster development, easier onboarding.
It's not about switching — it's about picking the right tool for the job.
It's not about switching — it's about picking the right tool for the job.
Both languages have their place — it really depends on what you're building.
If you're writing an OS, a device driver, or anything performance-critical where memory safety without a GC matters — Rust (or even Zig) is a great fit.
If you're writing an OS, a device driver, or anything performance-critical where memory safety without a GC matters — Rust (or even Zig) is a great fit.
May 29, 2025 at 5:35 PM
Both languages have their place — it really depends on what you're building.
If you're writing an OS, a device driver, or anything performance-critical where memory safety without a GC matters — Rust (or even Zig) is a great fit.
If you're writing an OS, a device driver, or anything performance-critical where memory safety without a GC matters — Rust (or even Zig) is a great fit.
I played a bit with it a few years ago but I don't have a lot of experience. Why?
May 29, 2025 at 4:36 PM
I played a bit with it a few years ago but I don't have a lot of experience. Why?