There’s more people blogging today than there’s ever been Unfortunately, all of their posts are locked in email inboxes or behind social network paywalls and not the open web

Nietzsche hits the mark once again.

"That's the shape that bit me..." Another classic ai trope that's super annoying. This one attempts to capture a few ones. tropes.fyi/tropes-md But I want to put names on each of these tropes. - negative parallelism - "it's not x, it's y" - anaphora - "no x. no y. just z" what else

I wonder if language-specific conferences are dead. Confs used to be a gathering of a bunch of curious & driven folks sharing stuff. Now all I see is sponsored slop or AI slop. Finding good talks has become harder and harder. The hallway convo is the only thing worth attending for now.

🎊 Go 1.27 Release Candidate 1 is released! 🏃‍♂️ Run it in dev! Run it in prod! File bugs! https://go.dev/issue/new 🔈 Announcement: https://groups.google.com/g/golang-announce/c/Cu9HkstbtpA/m/NfBgswyTBgAJ 📦 Download: https://go.dev/dl/#go1.27rc1 #golang

Wrote the classic "range over channel" goroutine leak while building a small custom cron scheduler. It's well-documented, & Uber included it as one of the most common #Go leaks. I've debugged it before in prod, but this shows how easy it is to write bugs like this. rednafi.com/go/channel-i...

If you are using #Go and do perf tracking, what does your continuous profiling stack look like? Raw pprof w/ manual scraping? Datadog? Pyroscope? Something else? Would love to know about your workflow.

Finally, got the time to read OpenAI's #Postgres scaling saga. Wild they sustained that kind of load with a single primary. But they also moved majority of their write load to CosmosDB. If your workflow is read heavy, you can go far with just adding replicas. openai.com/index/scalin...

Lol, this blew up on hackernews. It's always my yak shaving stories or bikeshedding posts that hit the frontpage. Never the ones that took days to write. news.ycombinator.com/item?id=4858...

One of the reasons I'm a #Go maximalist is that the core team focuses more on operational features than programming ones. Less syntax and more tooling, please. Go 1.27 will add a goroutine leak profile to the std tooling. Went down a rabbit hole with it this morning. rednafi.com/shards/2026/...

Every time I see "deskilling" I misread it as "desk killing", which it isn't but sorta is too.

I don’t know much about design & frontend work. But e/ LLM agents, exploring FE frameworks & design systems has been fun. W/o agents, I wouldn't explore the space b/c the JS ecosystem is such a shitshow. LLMs allow you to go wide & just have fun w/o trying to tie your career to every exploration.

Sticky bars in web design are super annoying - especially on smaller screens where vertical real estate is gold."

Good read on #Go nil check. But in defense of people doing overzealous checks - in large programs, sometimes tracking preceding nil checks are super hard. I am still a bit bummed Go didn't go for Rust like option types to do away with nils altogether.

It's time for other languages to ship basic operational toolings. CPU, memory, threads, & mutex profilers are a start. Runtime tracing should also be a part of every PL tooling. This way o11y vendors won't have to reinvent execution profiling, tracing, and metrics collection over and over again.

Observability Engineering, Second Edition is now off to the physical presses, after five rounds of quality control and review :)

Tried #nix. What a load of shite.

Guys, the “stop hiring humans” ads are bait. They’re designed to be angrily shared on social media to get them in front of as many eyeballs as possible. You can play a part in helping this strategy be less effective, by ignoring it

I was reminded of github.com/boldsoftware... by the @exe.dev crew also that might be worth a look!

A small part of me dies every time I have to say "link in the comments" - all because these walled gardens punish posts for including a URL. What a farce!

This has been lying around in my drafts for a while. #postgres 19 finally has an answer to the previously janky workflow for performing read-after-write. #MySQL has had this feature forever, but "WAIT FOR LSN" solves it in PG land. Took a while to write this one. rednafi.com/system/wait-...

Fable became funable.

I recently moved from #GNU stow to #chezmoi to escape symlink hellscape. Also, using it to lug around all my common agent skills across devices. Working fantastic so far. rednafi.com/misc/chezmoi/

The postmortem from Coinbase's 10-hour outage is out and... damn They run global trading from a single region because of latency. OK, I understand. BUT they have no automated failover prepared! Are they praying the region never goes down?? Doesn't compute for me...

Threaded #Rust is slower than concurrent, sloppily written #Go & async rust is a mess. But rust typesystem is nice for sure!

@bsky.app needs long form posts like twitter. One of the reasons the #AI twitter is so much more vibrant is that for some discussions, you need a little more space than 300 chars. Splitting the message breaks the cadence.

Few principles have been as useful in my day-to-day engineering work Walking Skeletons. It's also known as tracer bullet but I like the more dramatic name. [1/3]

What a honking great idea! It's quite encouraging that LLMs haven't killed off blogs and human written writeups. Also, cross linking is the only way uplift each other. Do it more please.

Had fun adding support for @standard.site to my blog. The richer preview card on #bsky looks neat. Another benefit is, since all the entries now live in the #ATmosphere, all kinds of #ATProto apps can index and display them. See pckt example: pckt.blog/read?search=... rednafi.com/misc/standar...

Yep ☺️ They even invited me to talk on the latest episode: youtu.be/cVkKKmNqIaA?...

This morning, I began making my blog @standard.site - compliant. I'm doing it post by post, starting with this one: preslav.me/2026/05/19/1... As of now, I don't know all the benefits, but I guess, I am about to find out soon. #golang

Thank you both @preslav.me @rednafi.com for sharing your insights. Ps. just listened to Cup n'go with you @preslav.me loved it mate ❣️ well deserved recognition to land on the podcast.

Look not to be crass but Anthropic's asinine insistence that their robot is the specialest boy and will *only* accept insertions from its specialest boy pointlessly brand-named directory is, in a word, bitchmade. It reeks of insecurity and a lack of confidence in the actual merits of the product.

TIL, #agent skills are becoming somewhat standardized. I hate the ~/.claude directory with the fire of a thousand suns. Why can't we just standardize on ~/.agents and have every harness pick it up? Instead, we're stuck with different directory structures for a bunch of freaking Markdown files.

new William Gibson book opening line dropped

Is anyone building an #LLM harness like Pi, but in #Go? I care about the language a tool is written in and want to avoid the JS/TS ecosystem entirely, regardless of the features. I mainly use codex because it's a Rust TUI, but a Go alternative would be great to hack around with.

Experimenting with @standard.site. @sequoia.pub makes it fairly easy to turn any static site into one that’s compliant with the spec. But I’ve tuned my CI to automate everything, so I never have to do anything manually. Write-up incoming. The preview looks fantastic! rednafi.com/go/typesafe-...

Why does every large company attempt to reinvent #observability once they get big enough? Sure, #datadog is expensive, but so are tokens. The LGTM/OTel soup is almost always worse than any of the known vendors. IDK how many hours I have lost stringing these clunky tools together.

I wish Bsky harbored half as much #LLM talk as Twitter. What did that platform do to scare away people who are doing frontier work with LLMs? I don't want to miss what's going on in that world, but logging into Twitter feels terrible most of the time.

I've been meaning to distill my thoughts on correlating shipped features with forced token usage for a while, as well as the repercussions of urging everyone to push code to the mainline. rednafi.com/zephyr/carry...

Inspired by @rednafi.com's recent post on whether one should wrap #golang errors or not, and some of my older stuff on the topic, I decided to sum up 10 of the most useful tips I found: preslav.me/2026/05/19/1...

i wonder what they are doing with the stackoverflow points these days

Good series of posts on Go logging by @rednafi.com “Go structured logging with slog” rednafi.com/go/structure... “Type-safe slogging” rednafi.com/go/typesafe-... #golang

Writing lots of agent automation these days. CC's internal ticker doesn't have enough o11y. So wrote a tiny CLI that allows me to schedule cron + fixed time jobs. All the state lives in a sqlite DB. I still drive it from claude but now I can track all the scheduled jobs. github.com/rednafi/eon

I really don't get the praise of Codex. I understand that not everyone is doing the same kind of programming w/ it. For me it's borderline useless. Autocompacts after 2 qs & then behaves like a lobotomized patient. I mostly do distsys and database work & claude code fares far better.

You can't look away forever. Pretending it's not for you. Hoping you can go on as always. Just try it once. And let it blow your mind. newsletter.appliedgo.net/archive/2026... #golang

PSA: Green Tea GC in go1.26 is incredible 🚀 This is what we saw for two big Go services. We'll try to gather more data and share it soon.

Just use slog for logging in #Go. This zerlog/zap APIs are a pain to deal w/. In 99% of cases, the few extra allocations made by slog simply doesn’t matter. W/ LLMs now I'm seeing clankers pulling in all three libs in the same codebase & making a mess out of it.

✨ New post Classic end of the month tradition that I have followed for over a decade now. A collection of links that I found particularly interesting in the past month and also some music recommendation for funky groove lovers. Enjoy ❣️ “Top picks — 2026 April” pawelgrzybek.com/top-picks-20...