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.
Go error handling is often criticized for being “too verbose.”
Swipe the carousel to see why that criticism misses the point.
#Golang #Go
Swipe the carousel to see why that criticism misses the point.
#Golang #Go
July 14, 2025 at 9:18 AM
Go error handling is often criticized for being “too verbose.”
Swipe the carousel to see why that criticism misses the point.
#Golang #Go
Swipe the carousel to see why that criticism misses the point.
#Golang #Go
These languages won’t get you a dev job tomorrow.
But they’ll teach you how to think, adapt, and face any coding challenge.
Hardcore? Sure.
But you don’t become a Jedi without sacrifice.
#Programming #CodeNewbie #LearnToCode #SoftwareEngineering
But they’ll teach you how to think, adapt, and face any coding challenge.
Hardcore? Sure.
But you don’t become a Jedi without sacrifice.
#Programming #CodeNewbie #LearnToCode #SoftwareEngineering
July 1, 2025 at 4:00 PM
These languages won’t get you a dev job tomorrow.
But they’ll teach you how to think, adapt, and face any coding challenge.
Hardcore? Sure.
But you don’t become a Jedi without sacrifice.
#Programming #CodeNewbie #LearnToCode #SoftwareEngineering
But they’ll teach you how to think, adapt, and face any coding challenge.
Hardcore? Sure.
But you don’t become a Jedi without sacrifice.
#Programming #CodeNewbie #LearnToCode #SoftwareEngineering
How Go's context package transforms chaotic goroutine sprawl into orchestrated control flow. From resource leaks to graceful cascading cancellations—context is the unsung hero of distributed Go systems.
#golang #programming
#golang #programming
June 4, 2025 at 8:00 AM
How Go's context package transforms chaotic goroutine sprawl into orchestrated control flow. From resource leaks to graceful cascading cancellations—context is the unsung hero of distributed Go systems.
#golang #programming
#golang #programming
DDD isn’t an architecture. It’s a mindset.
• Business logic becomes clear
• Code reads like user stories
• Bugs get squashed fast
• Features map to reality
It’s the difference between organizing code vs. understanding the business.
#cleancode
• Business logic becomes clear
• Code reads like user stories
• Bugs get squashed fast
• Features map to reality
It’s the difference between organizing code vs. understanding the business.
#cleancode
June 3, 2025 at 4:00 PM
DDD isn’t an architecture. It’s a mindset.
• Business logic becomes clear
• Code reads like user stories
• Bugs get squashed fast
• Features map to reality
It’s the difference between organizing code vs. understanding the business.
#cleancode
• Business logic becomes clear
• Code reads like user stories
• Bugs get squashed fast
• Features map to reality
It’s the difference between organizing code vs. understanding the business.
#cleancode
If you’re still scattering business logic across 15 files…
Read this.
DDD means:
• Business in one place
• Fewer bugs
• Clearer features
• Faster onboarding
It changed how I code and think.
#ddd
Read this.
DDD means:
• Business in one place
• Fewer bugs
• Clearer features
• Faster onboarding
It changed how I code and think.
#ddd
June 3, 2025 at 12:15 PM
If you’re still scattering business logic across 15 files…
Read this.
DDD means:
• Business in one place
• Fewer bugs
• Clearer features
• Faster onboarding
It changed how I code and think.
#ddd
Read this.
DDD means:
• Business in one place
• Fewer bugs
• Clearer features
• Faster onboarding
It changed how I code and think.
#ddd
MVC shows you where to put code.
DDD shows you what it should say.
• One place for business logic
• Domain-first thinking
• Less glue code, more clarity
I’d trade 5 years of patterns for 1 year of DDD.
#domainmodeling
DDD shows you what it should say.
• One place for business logic
• Domain-first thinking
• Less glue code, more clarity
I’d trade 5 years of patterns for 1 year of DDD.
#domainmodeling
June 3, 2025 at 8:30 AM
MVC shows you where to put code.
DDD shows you what it should say.
• One place for business logic
• Domain-first thinking
• Less glue code, more clarity
I’d trade 5 years of patterns for 1 year of DDD.
#domainmodeling
DDD shows you what it should say.
• One place for business logic
• Domain-first thinking
• Less glue code, more clarity
I’d trade 5 years of patterns for 1 year of DDD.
#domainmodeling
Context leaks in Go are silent killers.
They don’t crash your app — they slowly drain it.
Unreleased goroutines = invisible technical debt.
Fix it before it breaks you.
#golang #backend
They don’t crash your app — they slowly drain it.
Unreleased goroutines = invisible technical debt.
Fix it before it breaks you.
#golang #backend
June 2, 2025 at 7:00 PM
Context leaks in Go are silent killers.
They don’t crash your app — they slowly drain it.
Unreleased goroutines = invisible technical debt.
Fix it before it breaks you.
#golang #backend
They don’t crash your app — they slowly drain it.
Unreleased goroutines = invisible technical debt.
Fix it before it breaks you.
#golang #backend
The truth?
Rust is brilliant. But Go is a cheat code.
• Idiomatic Go in 2 weeks
• Real-world output day one
• No fighting with the compiler
Want velocity? Go wins.
Rust’s complexity isn’t worth it for most teams.
#programming
Rust is brilliant. But Go is a cheat code.
• Idiomatic Go in 2 weeks
• Real-world output day one
• No fighting with the compiler
Want velocity? Go wins.
Rust’s complexity isn’t worth it for most teams.
#programming
June 2, 2025 at 7:00 PM
The truth?
Rust is brilliant. But Go is a cheat code.
• Idiomatic Go in 2 weeks
• Real-world output day one
• No fighting with the compiler
Want velocity? Go wins.
Rust’s complexity isn’t worth it for most teams.
#programming
Rust is brilliant. But Go is a cheat code.
• Idiomatic Go in 2 weeks
• Real-world output day one
• No fighting with the compiler
Want velocity? Go wins.
Rust’s complexity isn’t worth it for most teams.
#programming
Most devs learn MVC first.
Big mistake.
You learn structure before meaning.
DDD flips it:
• You code business, not boxes
• Features shrink from days to hours
• Logic finally has a home
Learn the language before the grammar.
#softwaredesign
Big mistake.
You learn structure before meaning.
DDD flips it:
• You code business, not boxes
• Features shrink from days to hours
• Logic finally has a home
Learn the language before the grammar.
#softwaredesign
June 2, 2025 at 3:00 PM
Most devs learn MVC first.
Big mistake.
You learn structure before meaning.
DDD flips it:
• You code business, not boxes
• Features shrink from days to hours
• Logic finally has a home
Learn the language before the grammar.
#softwaredesign
Big mistake.
You learn structure before meaning.
DDD flips it:
• You code business, not boxes
• Features shrink from days to hours
• Logic finally has a home
Learn the language before the grammar.
#softwaredesign
You’re not building an OS.
You’re building CRUD APIs.
Stop over-engineering:
• Go gets new hires productive in days
• Rust drops team velocity by 50%
• Most apps don’t need a borrow checker
Choose speed over struggle.
#devlife
You’re building CRUD APIs.
Stop over-engineering:
• Go gets new hires productive in days
• Rust drops team velocity by 50%
• Most apps don’t need a borrow checker
Choose speed over struggle.
#devlife
June 2, 2025 at 5:30 AM
You’re not building an OS.
You’re building CRUD APIs.
Stop over-engineering:
• Go gets new hires productive in days
• Rust drops team velocity by 50%
• Most apps don’t need a borrow checker
Choose speed over struggle.
#devlife
You’re building CRUD APIs.
Stop over-engineering:
• Go gets new hires productive in days
• Rust drops team velocity by 50%
• Most apps don’t need a borrow checker
Choose speed over struggle.
#devlife
The most brilliant engineers I know don’t always pick the “best” tech.
They choose what yields the best results quickly.
• Go reads like English
• Devs ship in weeks
• Hiring is easy
• Teams move fast
Rust? It slows you down for marginal gains.
#softwareengineering
They choose what yields the best results quickly.
• Go reads like English
• Devs ship in weeks
• Hiring is easy
• Teams move fast
Rust? It slows you down for marginal gains.
#softwareengineering
June 1, 2025 at 6:45 PM
The most brilliant engineers I know don’t always pick the “best” tech.
They choose what yields the best results quickly.
• Go reads like English
• Devs ship in weeks
• Hiring is easy
• Teams move fast
Rust? It slows you down for marginal gains.
#softwareengineering
They choose what yields the best results quickly.
• Go reads like English
• Devs ship in weeks
• Hiring is easy
• Teams move fast
Rust? It slows you down for marginal gains.
#softwareengineering
Choosing Rust for CRUD services is like buying a jet to drive to work.
Sure, it’s fast.
But you’ll burn time, money, and team morale just trying to park it.
Go is simpler, faster, and way more practical.
You can use the right tool for the real-world job.
#backend
Sure, it’s fast.
But you’ll burn time, money, and team morale just trying to park it.
Go is simpler, faster, and way more practical.
You can use the right tool for the real-world job.
#backend
June 1, 2025 at 1:42 PM
Choosing Rust for CRUD services is like buying a jet to drive to work.
Sure, it’s fast.
But you’ll burn time, money, and team morale just trying to park it.
Go is simpler, faster, and way more practical.
You can use the right tool for the real-world job.
#backend
Sure, it’s fast.
But you’ll burn time, money, and team morale just trying to park it.
Go is simpler, faster, and way more practical.
You can use the right tool for the real-world job.
#backend
Sandbox mistakes don’t kill you.
They make you a real dev.
• Ask dumb questions
• Write ugly code
• Break your app
Then rebuild it stronger.
My journey through this cycle is in the newsletter today. #LearnToCode
https://thegolangblueprint.substack.com
They make you a real dev.
• Ask dumb questions
• Write ugly code
• Break your app
Then rebuild it stronger.
My journey through this cycle is in the newsletter today. #LearnToCode
https://thegolangblueprint.substack.com
https://thegolangblueprint.substack.com
The Golang Blueprint is a straightforward newsletter for self-taught and junior developers who want to move from tutorials to real engineering.
Every week, get practical insights on backend architecture, system design, debugging, and Golang. Click to read The Golang Blueprint, by Corentin Giaufer, a Substack publication. Launched a month ago.
thegolangblueprint.substack.com
May 28, 2025 at 9:00 AM
Sandbox mistakes don’t kill you.
They make you a real dev.
• Ask dumb questions
• Write ugly code
• Break your app
Then rebuild it stronger.
My journey through this cycle is in the newsletter today. #LearnToCode
https://thegolangblueprint.substack.com
They make you a real dev.
• Ask dumb questions
• Write ugly code
• Break your app
Then rebuild it stronger.
My journey through this cycle is in the newsletter today. #LearnToCode
https://thegolangblueprint.substack.com
The most humbling dev moment?
Passing all tests, then watching users get stuck.
• Tests ≠ UX
• Clever ≠ Clear
• Fancy ≠ Functional
These lessons hurt—but they stick.
The rest’s in this week’s newsletter. #SoftwareDev
https://thegolangblueprint.substack.com
Passing all tests, then watching users get stuck.
• Tests ≠ UX
• Clever ≠ Clear
• Fancy ≠ Functional
These lessons hurt—but they stick.
The rest’s in this week’s newsletter. #SoftwareDev
https://thegolangblueprint.substack.com
https://thegolangblueprint.substack.com
The Golang Blueprint is a straightforward newsletter for self-taught and junior developers who want to move from tutorials to real engineering.
Every week, get practical insights on backend architecture, system design, debugging, and Golang. Click to read The Golang Blueprint, by Corentin Giaufer, a Substack publication. Launched a month ago.
thegolangblueprint.substack.com
May 28, 2025 at 5:00 AM
The most humbling dev moment?
Passing all tests, then watching users get stuck.
• Tests ≠ UX
• Clever ≠ Clear
• Fancy ≠ Functional
These lessons hurt—but they stick.
The rest’s in this week’s newsletter. #SoftwareDev
https://thegolangblueprint.substack.com
Passing all tests, then watching users get stuck.
• Tests ≠ UX
• Clever ≠ Clear
• Fancy ≠ Functional
These lessons hurt—but they stick.
The rest’s in this week’s newsletter. #SoftwareDev
https://thegolangblueprint.substack.com
You won't get good by watching tutorials.
I tried that.
Real growth came from building messy, chaotic projects and fixing what broke.
The sandbox is where you level up.
Full article drops in the newsletter. #CodingTips
https://thegolangblueprint.substack.com
I tried that.
Real growth came from building messy, chaotic projects and fixing what broke.
The sandbox is where you level up.
Full article drops in the newsletter. #CodingTips
https://thegolangblueprint.substack.com
https://thegolangblueprint.substack.com
The Golang Blueprint is a straightforward newsletter for self-taught and junior developers who want to move from tutorials to real engineering.
Every week, get practical insights on backend architecture, system design, debugging, and Golang. Click to read The Golang Blueprint, by Corentin Giaufer, a Substack publication. Launched a month ago.
thegolangblueprint.substack.com
May 27, 2025 at 9:30 PM
You won't get good by watching tutorials.
I tried that.
Real growth came from building messy, chaotic projects and fixing what broke.
The sandbox is where you level up.
Full article drops in the newsletter. #CodingTips
https://thegolangblueprint.substack.com
I tried that.
Real growth came from building messy, chaotic projects and fixing what broke.
The sandbox is where you level up.
Full article drops in the newsletter. #CodingTips
https://thegolangblueprint.substack.com
I built and rebuilt the same app 5 times.
Not because I failed. Because I learned:
• Popular ≠ Practical
• 100% test coverage ≠ Usability
• Clever code ≠ Maintainable code
Each rewrite made me better.
Read how in today’s newsletter.
https://thegolangblueprint.substack.com
Not because I failed. Because I learned:
• Popular ≠ Practical
• 100% test coverage ≠ Usability
• Clever code ≠ Maintainable code
Each rewrite made me better.
Read how in today’s newsletter.
https://thegolangblueprint.substack.com
https://thegolangblueprint.substack.com
The Golang Blueprint is a straightforward newsletter for self-taught and junior developers who want to move from tutorials to real engineering.
Every week, get practical insights on backend architecture, system design, debugging, and Golang. Click to read The Golang Blueprint, by Corentin Giaufer, a Substack publication. Launched a month ago.
thegolangblueprint.substack.com
May 27, 2025 at 4:11 PM
I built and rebuilt the same app 5 times.
Not because I failed. Because I learned:
• Popular ≠ Practical
• 100% test coverage ≠ Usability
• Clever code ≠ Maintainable code
Each rewrite made me better.
Read how in today’s newsletter.
https://thegolangblueprint.substack.com
Not because I failed. Because I learned:
• Popular ≠ Practical
• 100% test coverage ≠ Usability
• Clever code ≠ Maintainable code
Each rewrite made me better.
Read how in today’s newsletter.
https://thegolangblueprint.substack.com
Most devs think mistakes mean failure.
But fighter pilots train in simulators. And we get sandboxes.
• Try fast
• Fail safely
• Learn deeply
This is the path to mastery.
Full story in this week’s newsletter. #SoftwareEngineering
https://thegolangblueprint.substack.com
But fighter pilots train in simulators. And we get sandboxes.
• Try fast
• Fail safely
• Learn deeply
This is the path to mastery.
Full story in this week’s newsletter. #SoftwareEngineering
https://thegolangblueprint.substack.com
https://thegolangblueprint.substack.com
The Golang Blueprint is a straightforward newsletter for self-taught and junior developers who want to move from tutorials to real engineering.
Every week, get practical insights on backend architecture, system design, debugging, and Golang. Click to read The Golang Blueprint, by Corentin Giaufer, a Substack publication. Launched a month ago.
thegolangblueprint.substack.com
May 27, 2025 at 4:05 PM
Most devs think mistakes mean failure.
But fighter pilots train in simulators. And we get sandboxes.
• Try fast
• Fail safely
• Learn deeply
This is the path to mastery.
Full story in this week’s newsletter. #SoftwareEngineering
https://thegolangblueprint.substack.com
But fighter pilots train in simulators. And we get sandboxes.
• Try fast
• Fail safely
• Learn deeply
This is the path to mastery.
Full story in this week’s newsletter. #SoftwareEngineering
https://thegolangblueprint.substack.com
Stop trying to write "perfect" code as a beginner.
My early Go app: 6 layers, 3 frameworks, total mess
My rewrite: Just stdlib, 10x faster
Your "failures" teach more than tutorials.
#coding #webdev #buildinpublic
My early Go app: 6 layers, 3 frameworks, total mess
My rewrite: Just stdlib, 10x faster
Your "failures" teach more than tutorials.
#coding #webdev #buildinpublic
May 27, 2025 at 10:00 AM
Stop trying to write "perfect" code as a beginner.
My early Go app: 6 layers, 3 frameworks, total mess
My rewrite: Just stdlib, 10x faster
Your "failures" teach more than tutorials.
#coding #webdev #buildinpublic
My early Go app: 6 layers, 3 frameworks, total mess
My rewrite: Just stdlib, 10x faster
Your "failures" teach more than tutorials.
#coding #webdev #buildinpublic
Want to build stunning CLI tools in Go?
Use Bubbletea.
• Beautiful text UIs
• Elegant architecture
• Fun to use
Make your terminal apps feel like magic.
#cli #golang #opensource
Use Bubbletea.
• Beautiful text UIs
• Elegant architecture
• Fun to use
Make your terminal apps feel like magic.
#cli #golang #opensource
May 27, 2025 at 6:00 AM
Want to build stunning CLI tools in Go?
Use Bubbletea.
• Beautiful text UIs
• Elegant architecture
• Fun to use
Make your terminal apps feel like magic.
#cli #golang #opensource
Use Bubbletea.
• Beautiful text UIs
• Elegant architecture
• Fun to use
Make your terminal apps feel like magic.
#cli #golang #opensource
Tired of "works on my machine"?
Use Dev Containers.
• Instant dev environment setup
• Reproducible across the team
• All dependencies pre-installed
No more setup hell. Just code.
#devcontainers #docker #devops
Use Dev Containers.
• Instant dev environment setup
• Reproducible across the team
• All dependencies pre-installed
No more setup hell. Just code.
#devcontainers #docker #devops
May 26, 2025 at 2:45 PM
Tired of "works on my machine"?
Use Dev Containers.
• Instant dev environment setup
• Reproducible across the team
• All dependencies pre-installed
No more setup hell. Just code.
#devcontainers #docker #devops
Use Dev Containers.
• Instant dev environment setup
• Reproducible across the team
• All dependencies pre-installed
No more setup hell. Just code.
#devcontainers #docker #devops
The best messaging system I’ve used in 2025: NATS.
• Lightning-fast pub/sub
• Lightweight & reliable
• Supports clustering + persistence
Easier than Kafka. More robust than Redis. Built for scale.
#eventdriven #golang #scalability
• Lightning-fast pub/sub
• Lightweight & reliable
• Supports clustering + persistence
Easier than Kafka. More robust than Redis. Built for scale.
#eventdriven #golang #scalability
May 26, 2025 at 8:00 AM
The best messaging system I’ve used in 2025: NATS.
• Lightning-fast pub/sub
• Lightweight & reliable
• Supports clustering + persistence
Easier than Kafka. More robust than Redis. Built for scale.
#eventdriven #golang #scalability
• Lightning-fast pub/sub
• Lightweight & reliable
• Supports clustering + persistence
Easier than Kafka. More robust than Redis. Built for scale.
#eventdriven #golang #scalability
Go-task made me ditch Makefiles for good.
• YAML-based task runner
• Dependency-aware
• Cross-platform
• Built-in variable support
Cleaner builds, easier automation. Perfect for Go projects.
#golang #buildtools
• YAML-based task runner
• Dependency-aware
• Cross-platform
• Built-in variable support
Cleaner builds, easier automation. Perfect for Go projects.
#golang #buildtools
May 26, 2025 at 5:30 AM
Go-task made me ditch Makefiles for good.
• YAML-based task runner
• Dependency-aware
• Cross-platform
• Built-in variable support
Cleaner builds, easier automation. Perfect for Go projects.
#golang #buildtools
• YAML-based task runner
• Dependency-aware
• Cross-platform
• Built-in variable support
Cleaner builds, easier automation. Perfect for Go projects.
#golang #buildtools
Debugging microservices used to be painful—until Jaeger.
• Full request tracing
• Visual bottleneck mapping
• Instant visibility into distributed systems
If you're scaling services, this is non-negotiable.
#microservices #observability #devops
• Full request tracing
• Visual bottleneck mapping
• Instant visibility into distributed systems
If you're scaling services, this is non-negotiable.
#microservices #observability #devops
May 25, 2025 at 8:45 PM
Debugging microservices used to be painful—until Jaeger.
• Full request tracing
• Visual bottleneck mapping
• Instant visibility into distributed systems
If you're scaling services, this is non-negotiable.
#microservices #observability #devops
• Full request tracing
• Visual bottleneck mapping
• Instant visibility into distributed systems
If you're scaling services, this is non-negotiable.
#microservices #observability #devops
The single best Go code quality tool: golangci-lint.
• Runs 40+ linters
• Catches bugs pre-commit
• Flags performance issues
• Integrates seamlessly into CI/CD
Set it up once. Let it guard every PR. #golang #devtools
• Runs 40+ linters
• Catches bugs pre-commit
• Flags performance issues
• Integrates seamlessly into CI/CD
Set it up once. Let it guard every PR. #golang #devtools
May 25, 2025 at 4:30 PM
The single best Go code quality tool: golangci-lint.
• Runs 40+ linters
• Catches bugs pre-commit
• Flags performance issues
• Integrates seamlessly into CI/CD
Set it up once. Let it guard every PR. #golang #devtools
• Runs 40+ linters
• Catches bugs pre-commit
• Flags performance issues
• Integrates seamlessly into CI/CD
Set it up once. Let it guard every PR. #golang #devtools
The six #backend tools that transformed how I build production systems in 2025.
After 4 years of coding 7/7, these are the non-negotiable tools in my stack.
Thread 👇
After 4 years of coding 7/7, these are the non-negotiable tools in my stack.
Thread 👇
May 25, 2025 at 12:53 PM
The six #backend tools that transformed how I build production systems in 2025.
After 4 years of coding 7/7, these are the non-negotiable tools in my stack.
Thread 👇
After 4 years of coding 7/7, these are the non-negotiable tools in my stack.
Thread 👇