So, I Wrote a Book: The Story Behind 100 Go Mistakes
An brutally honest behind-the-scenes story of writing a technical book from scratch. From burnout to unexpected wins, here's everything I learned while writing 100 Go Mistakes.
languages
golang
Goroutines in Go: A Practical Guide to Concurrency
Let’s face it: modern apps often need to do a million things at once. If your app isn’t set up for that, it can feel clunky and slow. That’s…
Go Optimization Guide
Patterns and Techniques for Writing High-Performance Applications with Go
Timeout Middleware in Go: Simple in Theory, Complex in Practice - Viktor Nikolaiev's blog
What happens when we need different timeout durations for different endpoints? While implementing timeouts might seem straightforward at first glance, the most obvious solution fails silently, frustraiting both users and developers.
Session-Based Authentication in Go
Implementing session-based authentication in Go web applications: a secure and efficient approach.
Go Structs and Interfaces Made Simple
When developers transition to Go from object-oriented languages like Java, C++, or Python, they often struggle with Go’s approach to types a…
Struct Optimizations in Go
In this article we will look into optimizing memory usage and CPU performance by designing our Go structs with the CPU word size and cache line size in mind.
Slice Internals in Go: How the Runtime Expands Slices Efficiently
This article dives into the internals of Go slices, exploring how the runtime efficiently grows the slice’s backing array. It covers the key strategies used, including growth factors, CPU word size alignment, and the size class allocation table, all aimed at optimizing performance while maintaining flexibility.
Bundling Past, Present, and Future
A recent talk I gave about JavaScript bundlers. It’s a bit of a history lesson, and along the way I tried to introduce what bundlers are, why you’d use one, ...
javascript
4 Ways of Bumping Major Versions in Your Go Project
I've recently found myself in a rabbit hole of Go major version bumping to v2. What started as a simple task quickly turned into hours of sifting through conflicting information. Should I use a v2 directory? Create a new v2 branch? What about creating a new repository altogether?
The more
The Business of Go - Cameron Balahan, Google
Millions of developers love Go for its features, performance, ecosystem, and community. But there’s another, perhaps more compelling reason as well: Go is go...
Why is Golang's Compilation Speed So Fast? | PixelsTech
OverviewWhen I started learning the Go language, I already had experience with three statically typed languages—C/C++ and Java—and two dynamically typed languages—PHP and JavaScript.
Writing secure Go code | Jakub Jarosz
What does it mean to keep security in mind when writing Go code? Answering this question in one short article seems impossible. For this reason, we will narrow it down to a few specific practices.
Lessons learned from a successful Rust rewrite
rustGo Plan9 Memo, Speeding Up Calculations 450% | Jacob_Ray_Pehringer
korean
packagemain #28: How to work with GitHub API in Go - YouTube
In this episode we create a GitHub OAuth application in Go that lets users authenticate with GitHub and calls GitHub API on their behalf.
Code: https://github.com/plutov/packagemain/tree/master/28-github-api
GitHub API Go Client: https://github.com/google/go-github
Fun project I built recently: https://gitprint.me
Our Substack: https://packagemain.tech
Follow me on X: https://x.com/pliutau
When I told 4,091 writers they weren’t getting paid
Subtle database errors and how we recovered
Russ Cox on passing the torch with Austin Clements & Cherry Mui (Go Time #333)
• Introduction of guests and their roles on the Go team
• Russ Cox’s decision to step down as tech lead of the Go project
• Transition of leadership roles: Austin Clements taking over as Go project tech lead and Cherry Mui becoming tech lead of the Go core team
• Discussion on the personal backgrounds of Austin and Cherry, including how they got into Go
• Austin and Cherry’s initial thoughts and goals for their new leadership roles
• Russ Cox’s explanation of the importance of leadership transition for the Go project
• Austin’s perspective on the role of a tech lead and its responsibilities
• Cherry’s explanation of what the Go core team is and her thoughts on leading it
• Russ Cox’s new role in exploring AI applications for the Go project, particularly in aiding software maintenance
• Austin’s focus on stability, engineering at scale, and potential improvements in performance engineering in Go
• Cherry’s focus on scaling Go to handle modern hardware trends and user needs
• Community engagement and communication between the Go team at Google and the broader Go community
• Discussions on the barriers between the Go team and the community, and how to reduce them
• How to get involved or stay updated on Go’s development (forums, proposals, code reviews, conferences)
• Unpopular opinions from the guests, including Russ’s preference for Boston as the best place for software engineers, Cherry’s dislike of the GitHub pull request workflow, and Austin’s view on tech debt being manageable and sometimes beneficial.