Redowan Delowar

"Partial updates with field masks" by @rednafi.com Classic post by Redowan. On point as always. Real world problem statement, and good practical solution. This one not strictly Go lang specific. rednafi.com/go/patch-fie... #api #grpc

Field masks is a neat trick to make the update semantics of your API more tractable. rednafi.com/go/patch-fie...

I don’t understand the distribution mechanism of this site. Now that all the tech people are back on twitter, this site lost quite a bit of lusture. On top, most of my posts just aren't seen by many compared to X. I have same follower count there and I don't pay for premium. Sorta strange.

SKILLs are alright but keeping the long ones up to date is a pain. Also, I don't like how models load up all the skill descriptions in context and read them ad hoc. I'm glad that Pi harness kept the prompt templates. Super quick to write one and keep them up-to-date.

Astra is really, really cool but I cannot current trust it for my present day engineering. At least until I have adjusted. Some random thoughts including code samples of what I recovered from my traces. lucumr.pocoo.org/2026/9/7/ast...

If you use AI less than I do, you just don’t get it. If you use AI more than I do, you’ve fucking lost it. The optimal amount of AI is exactly how much I currently use.

@rednafi.com another point for Pi earendil.com/posts/there-... TL;DR: it seems to fit well both power users and non tech people alike

I love Go, I love Pi. I'm also a simple person, so I share: rednafi.com/misc/pi-harn... by @rednafi.com PS blog already in my /blogroll, but this deserves special mention

I am so mad that, despite hearing about the Pi harness from when it was devised, it took me this long to start using it. My workplace injects quite a bit of skills, mcps & other bloat into cc & codex, and Pi takes 2 minutes to clean that up. Also, it doesn't bloat my context.

Frontier LLMs are much better and dramatically faster than I am at finding and fixing bugs. If you are not asking them to debug your code and review your bugs, you are doing it wrong. A thread of Claude wins. (No longer at Google, btw.)

Wrote a tiny #Go based cron/at scheduler that doesn't depend on the system daemons. Been using it for a few months. Then someone reached out saying that they used it as a code review example for their interns and found an actual bug. So I dusted it off yesterday. github.com/rednafi/eon

Still too lazy to run open models locally. I have a beefy enough machine but not yet completely happy with the performacne & quality of the output. Also, my employer is footing the bill for now. So there's less motivation. But I am absolutely rooting for them to bring the cost down for everyone.

People sometimes ask whether our choice of programming language matters anymore, now that AI writes so much of our code for us. As @rseroter.bsky.social and I write, our choice of programming language actually matters more than ever. developers.googleblog.com/why-go-is-an...

If AI really makes developers anywhere near 10x more productive, the notable absence of any significant new or improved products would suggest maybe developers have never been as singularly important to the process of making ideas successful as developers have enjoyed the privilege of believing.

TIL a nice #GoLang trick! That doesn't happen so often these days. :D

A really nice blog post about fire-and-forget with in-memory queue in Go from @rednafi.com. It can be used in projects if you need a simple, asynchronous, in-memory queue implementation. 🔗 rednafi.com/go/supervise...

They are saying this like it's a bad thing. This lame stat only proves that trans folks are better programmers than your average right-wing nut. What's wrong with these people. Just let people be! x.com/LundukeJourn...

Async Rust is so bad that even reading the chapter in rustbook feels like a chore. The book compensates it by importing a small crate that abstracts away tokio and all the machineries. It's super hard to go from preemptive concurrency of Go to the same old colored future based cooperative conc.

We have oriented our society in ways where - someone can't say they dislike something w/o elaboration - someone can't change their mind w/o getting heat from the mob For example: I used to not like #Rust but it grew on me as I use it more. But also, the Rust community is ass.

I find top down learning schemes a big scam to lure in people w/ ADHD. It took a few years for me to pick up my 2nd PL & a few more to ship code to prod. Reading books, blogs, watching talks, & working on the go is a linear process and going top down means skipping steps...and that has tradeoffs.

Any post that talks about caching but doesn't mention invalidation and stampede should be taken with a grain of salt.

Speedrunning through the Rust book. Landed on Chapter 7. I like how expressive the type system is, but I also don't like how expressive the type system is. You could play around with enums, matches, & trait bounds for days without building anything. But intellectually, it's extremely satisfying.

The ops story for #Go keeps on getting better.

Go Compile-Time Instrumentation just hit v1! 🎉 Add OpenTelemetry to your Go services with zero code changes. Swap go build for otelc go build and get automatic instrumentation for your app, dependencies & the standard library. opentelemetry.io/blog/2026/go...

first time using oai models for coding. it's so refreshing to ask it simple questions and for it to reply immediately rather than using 300 tool calls and taking 30 minutes

Oh look who arrived!

I write a lot of Go and TS for both work & play and I am loving #Rust. The compile time is atrocious and Rust analyzer is a huge pain in anything beyond 10k loc. Oh async is a mess and not half as ergonomic as Go but the typesystem is 🤌

#Meetup app is so shit that I am surprised they haven't been wiped out by some AI powered competition. Their legacy database is their moat but otherwise we should have moved away from that crap ages ago. Rootly whacked pagerduty for on similar ground. Need a rootly for meetup.

New blog post: GC shape stenciling in #Go generics. Go takes a hybrid approach between full monomorphization and type erasure to implement generics. This way the compile time remains fast but it does introduce some runtime overhead. rednafi.com/go/gc-shape-...

To native English speakers: Isn't the cringe in LLM-generated text obvious? How does anyone not notice the overuse of adjectives, anaphora, em dashes, and comma-infected compound sentences? No one talks like this. How does anyone miss it?

I mean, why pay for AI when you can wait for some schmuck to fire one at your GitHub repo and just ask it to do whatever the hell you want!??

TypeScript is now officially written in Go.

"We do autonomous agentic development but we are not vibe coders. We only allow the highest quality code to be pushed to prod." How do you know that it's high quality? Do you review everything?" "Nope, other agents do. And we got SKILLz" Then you look at the code & find that it's utter garbage.

LLM capabilities has hit an asymptote for what I do. It literally doesn't matter if I am working with 5.5, 4.8 or Fable. If you don’t do vibe slopping, looping or other retardmaxxing, and use LLMs as accelerator for your existing SDLC workflow, the capability gains are marginal.

Just because I am traveling to a place doesn't make me an expert in the local language. Many apps do this. Why would you change the default language based on location if the user is already logged in? Utter stupidity.

A friend of mine received this text message after a support call. Our AI overlords may just lick us to death with cringe.

Sorry for the delay, here is the link. docs.google.com/presentation...

Did the idea of threading together a bunch of Lambda, SQS, and SNS services to build your system ever pan out well? In every substantial project I’ve seen, this design turned into an absolute catastrophe for the maintainability & understandability of the system. I wanna hear some success stories.

Another great post by @rednafi.com for go lang devs. This time all about modernizers and `go fix` CLI tool. "Modernizers & go fix" rednafi.com/go/gofix/ #golang

#Go 1.26 revived the "go fix" command to migrate older APIs to the latest ones. Super satisfying to run it on a large codebase and see it purge all the old cruft. Blog post: rednafi.com/go/gofix/

People futzing w/ subagents team, long running agents, The Loop are also the group that produces dogshit code. Ignoring Twitter yappers w/ questionable incentives, most effective folks I work w/ are using single agents and occasionally some subagents. Experience & good judgement are still in vogue.