mastodon 4.7.2From Code to Clarity: Making Complex Technology Accessible
When type systems bring type checkers to their limit, naming things is still an art, and tests don't target business logic, then it's time for another Applied Go Weekly Newsletter.
#golang
https://newsletter.appliedgo.net/archive/2026-03-29-turning-insights-into-pages/?utm_source=appliedgo-mastodon
Nothing brings developers together quite like hating the same framework. This week: Gin
https://newsletter.appliedgo.net/archive/2025-12-14-spilling-the-gin/?utm_source=appliedgo-mastodon
#golang
https://newsletter.appliedgo.net/archive/2025-12-14-spilling-the-gin/?utm_source=appliedgo-mastodon
https://appliedgo.net/spotlight/lethal-trifecta-avoid-with-go/The Lethal Trifecta is a systemic weakness of LLMs, but only if you let it happen.
(Side note: This post is three weeks late; I shared it in my newsletter already, but another "lethal trifecta" of Hugo deprecations, caching quirks, and iCloud Drive hiccups prevented me from updating the blog in time. Well...)
https://appliedgo.net/spotlight/lethal-trifecta-avoid-with-go/
https://appliedgo.net/spotlight/lethal-trifecta-avoid-with-go/
The perfect tool to fix old code.
Ten mantras for writing perfect code.
And a perfect case for dumbing down LLMs with code.
https://newsletter.appliedgo.net/archive/2026-02-22-perfect/?utm_source=appliedgo-mastodon
#golang
https://newsletter.appliedgo.net/archive/2026-02-22-perfect/?utm_source=appliedgo-mastodon
Go 1.26 is out, and what I like most (so far) is the brand new `go fix` command. Forget all you know about the old `go fix` (if you even have been aware of its existence).
#golang
https://newsletter.appliedgo.net/archive/2026-02-15-if-it-aint-broken-go-fix-it/?utm_source=appliedgo-mastodon
For convenient coding, you need an interpreted language.
For writing fast apps, you need a low-level system language.
Excuse me, that's complete rubbish.
https://newsletter.appliedgo.net/archive/2025-12-07-from-slow-to-go/?utm_source=appliedgo-mastodon
#golang
https://newsletter.appliedgo.net/archive/2025-12-07-from-slow-to-go/?utm_source=appliedgo-mastodon
Newsletter = Issue [ ',' Issue ] .
Issue = Title Content .
Title = '# ' Words NL NL .
Content = { Heading Body } .
Heading = '## ' Words NL NL .
Body = Words NL NL .
Words = Punctuation Space ] [ Word [ Space .
Word = Letter [ { Letter } ] .
Letter = `[A-Za-z]` .
Punctuation = '.' | ',' | ':' | ';' | '!' | '?' | '(' | ')' | '-' | '–' | '—' .
Space = ' ' | NL
NL = '\n' .
(Don't expect this to compile.)
#golang
https://newsletter.appliedgo.net/archive/2026-02-08-what-came-first-the-token-or-the-egg/?utm_source=appliedgo-mastodon
A client judges a contractor by their output, not by how they achieve that output. Your unit tests should do that, too.
#golang
https://newsletter.appliedgo.net/archive/2026-02-01-test-your-contracts/?utm_source=appliedgo-mastodon
- The Go Developer Survey
- How to mock dependencies without a mocking library
- Write a compiler
The latest Applied Go Weekly Newsletter is here!
#golang
https://newsletter.appliedgo.net/archive/2026-01-25-the-shift-that-did-not-come-yet/?utm_source=appliedgo-mastodon
Make better AI with Go. Make better Go apps with AI.
(Heck, or just make silly AI and silly Go apps—just have fun!)
A programming language's version number that corresponds to the last two digits of the year the version is released is like a blue moon, just rarer. (Except if the versions are released yearly, or carry the year in their "version", but that's not the case with Go.)
https://newsletter.appliedgo.net/archive/2026-01-11-2026-and-go-126/?utm_source=appliedgo_mastodon
https://newsletter.appliedgo.net/archive/2026-01-11-2026-and-go-126/
If you want to write good, performant software, become friends with the hardware. No, I'm not talking about the Stockholm Syndrome.
#golang
https://newsletter.appliedgo.net/archive/2025-11-30-mechanical-sympathy/?utm_source=appliedgo-mastodon
- Go turns 16
- How Go and Rust differ
- The Go ecosystem in 2025
Another Applied Go Weekly Newsletter issue!
https://newsletter.appliedgo.net/archive/2-4-happy-birthday-go/?utm_source=appliedgo-mastodon
#golang
https://newsletter.appliedgo.net/archive/2-4-happy-birthday-go/?utm_source=appliedgo-mastodon
Nah, the gems in the latest Applied Go Weekly Newsletter issue aren't hidden; they're in plain sight.
The hidden ones are in the first featured article.
https://newsletter.appliedgo.net/archive/2026-01-18-hidden-gems/?utm_source=appliedgo-mastodon
#golang
https://newsletter.appliedgo.net/archive/2026-01-18-hidden-gems/?utm_source=appliedgo-mastodon
When data comes in, undistilled
Get dozens of workers to build
Collect the result
When they come to a halt
And the buffer is readily filled
(Limerick handmade with love, so all bad rhyming is on me. I only asked Claude to find words that rhyme with undistilled. Is this cheating?)
https://newsletter.appliedgo.net/archive/2025-11-23-map-it-reduce-it-buffer-it-profile-it/?utm_source=appliedgo-mastodon
Simon Willison has a hilarious way of producing his newsletter:
"It’s 143 lines of convoluted SQL that assembles most of the HTML for the newsletter using SQLite string concatenation! (...) This is a _terrible_ way to assemble HTML, but I’ve stuck with it because it amuses me."
https://simonwillison.net/2025/Nov/19/how-i-automate-my-substack-newsletter/#atom-everything
