Redowan Delowar

@rednafi.com

Roving amateur fumbling through software, systems, & sundry. Engineering @Doordash/Wolt Writing rednafi.com Currently in Berlin, Germany

Finished reading the DSQL paper. It's surprisingly readable. While the early 2010s era evangelized eventual consistency everywhere, recent years have harkened back to strongly consistent DBs. But this time you get snapshot isolation in a multi-region active-active DB.

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.

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.

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.

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

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.

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!??

"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.

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

It reads: Thank you for sharing this little moment in time with me. Your kindness and patience have felt like a gentle light throughout our conversation. Before our paths drift apart for now, While we are connected, can I confirm your issue is resolved? Let me know if you have any different or additional query that I can sort for you today.

(Botched grammar and punctuation as in the original.)

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.