Buil[d|t] To Learn Hi , Sometimes, building a project is the best way to learn a particular topic. As a close second, inspect projects built by others to...

Go Faster With Green Tea Hi , Go's garbage collector has gone through a remarkable journey. In Go 1.5, the Go team implemented a tri-color concurrent...

Practice Best Practices Hi , Hey, psst! Wanna have some tips for writing better Go? Here you are: Two articles about enhancing your coding, one about making...

Literate Scripting Hi , A compiled language usually isn't designed to be a good scripting language. Go isn't either, but projects like Mage, Yaegi, or...

The Cost Of (Avoiding) Dependencies Hi , From custom SQL backends to time as a performance bottleneck: Another week of Go (and not-so-Go-ish) news. Enjoy!...

Enjoy The Flight! Hi , Q4 has begun, and the Applied Go Weekly Newsletter isn't quite dead yet. Au contraire, mon ami, I am busy optimizing my workflow to...

Never Get Bored With The Basics Hi , Are you ready for a journey? I am planning to do a Spotlight series about building a basic SaaS platform for...

So You Don't Like Go? Hi , Awww, the 2nd issue after the summer break! I wanted to use the break for streamlining and automating my newsletter editing...

Commit Messages That Write Themselves Hi , The final 🌴 Summer Break 🌴 issue is in your inbox! With this issue, I'm concluding the AI series and looking...

Rodents of Unusual Size? I don't believe they exist. There’s endless discourse around tech debt. Kellan has some really good categorizations of different types, Will Larson has a great explainer of organization debt in his book, and I also like the idea of product debt. Throughout my career, I’ve been an engineer complaining about tech debt, a manager prioritizing (and deprioritizing) addressing tech debt, and a product manager, where I assume I primarily inspire the creation of new tech debt.

Blue Gopher Meets Stochastic Parrot Hi , Geez, the previous Spotlight was a bit long and code-heavy (for a Spotlight), wasn't it? Even though this newsletter...

You're Lucky: Full Moon Tonight! Hi , This is the second of four 🌴 "Summer Break" 🌴 issues with reduced content. As you may have guessed when you read the...

Let's ask an LLM Hi , This newsletter is in 🌴 Summer Break Mode 🌴 until August 24th, which means reduced content, and I decided to take the opportunity to...

An easy-to-use workflow automation library for Go. Supports conditional branching, parallel execution, embedded scripting, and execution checkpointing. Think of it like a lightweight hybrid of Temp...

New And Improved Formula! Hi , In this corner: JSON, the champion of sloppy data constructs. In the opposite corner: Go, the guardian of rigid data...

Fighting cross-site request forgery (CSRF) becomes easier in Go 1.25, thanks to the new cross origin protection feature.

Short tips, essays, and news about working with Go and software development. Most spotlights originate from my [Go newsletter](https://newsletter.appliedgo.net/archive).

Don’t Mess With My Site! Hi , There are myriad ways of attacking a web app, and cross-site request forgery is a particularly perfidious way of hijacking an...

Before Go 1.25, GOMAXPROCS defaults to the number of available physical CPU cores at app startup time. Now it takes container limits into account and checks changes periodically.

WaitGroups are a means of synchronizing goroutines; yet the Add()/defer Done() idiom feels clumsy and is error-prone. A new method, Go(), puts an end to goroutine counting.

(Don't) Leave No Trace Hi , Logs and traces are nice and useful ... until they start filling your disks. It would be much better to capture only the...

Know Your (CPU) Limits! Hi , Living beyond one's means is rarely a smart move. But it's easy to get their if you aren't aware of your limits. Go apps have...