We need to talk about Ralp loops

We need to talk about Ralp loops

Link: https://youtu.be/Yr9O6KFwbW4

Context

It kind of is hillarious of how this works! I am not able to wrap my head around it. Like why and how What kind of … Writing it immediately hit me. I do the same thing that Ralph loop does with AMP code free tier. The context size is limited, so I have to be wary of the limit, I keep the summary of the thread once the limit is reached and continue a new thread. Wow. Writing actually makes things visible and find the hidden patterns. Gold! Watching this video now makes sense. It just a loop for agent to start from where it left off without bloating the context. Superb.

Welcome to Gas Town

Welcome to Gas Town

Link: https://steve-yegge.medium.com/welcome-to-gas-town-4f25ee16dd04

Context

Agents as code generation orchestrators. This is quite a ambitious thing. I haven’t read the full post. But I can see where it goes. I haven’t either been in situations with 10s of these agents ripping in the background. There are reasons for them and some of them I am trying to overcome. I don’t have that many ideas honestly, this is flawed in my opinion, my biggest weakness maybe. I don’t have claude code as I don’t have much to spend on AI. I am limited by free options and some work related subscriptions. I am bogged down by the clumsy free models. The habit of abandoning a project after the setup is too evasive now. The earlier habit has just got more notorious with AI. That all said, I love this idea, the next step in AI is agents orchestration. Maybe I am behind it, but I had a few ideas, not exactly this but some level of parallel agents running. Not orchestrating. Maybe that idea is speaking more than ever. I thought someone solved it, but nope. Need to roll up the sleeves.

Writing first tooling second

Writing first tooling second

Link: https://susam.net/writing-first-tooling-second.html

Context

True, gold. This is to the point and another way of saying, “Show, don’t tell”, so “Write, don’t setup” The blog is merely one possible organising principle, not a requirement. I started the same way. I picked up hashnode, then moved to jekyll and github pages, then used python via markata (waylon walker’s ssg), an ssg that someone else wrote and I loved it, it was what I needed, the control of what goes in and out and also it was easy to see what was happening so that I can change and remove what I wanted. I finally now am rolling my own SSG in Golang and a CMS system. I am not very consistent in sticking to one cms, I have built 3-4 versions of them. But the thing is I still post consistently. Not long form posts, but these reflective posts and short bursts of thinking. Write your brain out first, then eventually it will outgrow to your needs, the system will be formed not shoved in. Like earlier I just used to write long form how-to-guides or tutorials, then I started to write reflections weekly, then link posts tils and suddenly I had 10 types of posts. Article, Tutorials, TILs, Thoughts, Link-blog, Newsletter, Notes, and what not.

The recurring dream of replacing developers

  • what a flashback, everything makes sense.
  • Programming is not mechanical
  • yet people tried hard to make solve for it as it was mechanical
  • COBOL made syntax readable. CASE tools eliminated typing. Visual tools eliminated syntax. AI can now generate entire functions from descriptions
  • Each advancement addressed a real friction point. Yet the fundamental challenge persists because it’s not mechanical. It’s intellectual. Software development is thinking made tangible
  • Just sheer facts those two. We need to find a way around using AI not away from it.

A Letter for those who fired Tech Writers because of AI

Preview

Hey you, Yes, you, who are thinking about not hiring a technical writer this year or, worse, erased one or more technical writing positions last year because of AI. You, who are buying into the promise of docs entirely authored by LLMs without expert …

A Letter for those who fired Tech Writers because of AI

Link: https://passo.uno/letter-those-who-fired-tech-writers-ai/

Context

True empathy is key Liability, everything becomes liability if outsourced. LLMs don’t have the taste, the care feeling of the users, the developers yet.

Source: techstructive-weekly-77