Background
Go is the language I genuinely enjoy working in the most. The speed, the strong type system, and the module structure, which honestly reminds me of the DDD-style organization I use in Laravel, just baked directly into the language all click with how I like to think about code. It rewards clarity and discipline, and the feedback loop from writing to running is fast enough to keep momentum on whatever I’m building.
Why it resonates
Coming from PHP and Laravel, Go’s approach to structuring code feels familiar but stricter. No magic, no hidden behavior. Just explicit, readable modules that compile to a single binary. That directness is what draws me to it over other compiled languages.
How I Use It
Go is my go-to when I want to push beyond what PHP can comfortably handle, or when I want to explore an idea in a language that forces me to think about structure upfront. It’s where I tinker, prototype, and build tools for my own workflow.
Where Go shows up
- Prototyping: performance-sensitive ideas that need more than PHP can offer
- CLI tooling: internal tools and automation that benefit from single-binary deployment
- Daily tooling: I deliberately rely on Go-built tools like lazygit and lazysql in my workflow
- Learning by using: staying close to the Go ecosystem even outside of writing it
I haven’t shipped a production client application in Go yet — most of my work here lives in prototypes and personal projects but it’s a language I keep investing in because I enjoy it.
Status
Active: prototyping, tooling, and personal projects.