> What started as a community experiment is becoming infrastructure. The developers behind Ralph and Taskmaster figured out something real. Now the platforms are catching up.
> That’s usually how it goes. The practitioners find the patterns first. Then the patterns become features.
This is the scariest thing atm with the fast pacing of these things. As capabilities increase, everything you've spent time on building (w/ scaffolding, tooling, etc) gets "merged" into the all-you-can-prompt solution that the big labs provide. If your previous work has no differentiation, it's very hard to provide additional value / monetise it. And it's hard to know what will be differentiation or what will get eaten up.
It's that sci-fi story trope of the colony ship that gets overtaken by a new generation engine, and when they reach their planet they find a thriving colony there already. But with software :)
Even funnier is ghuntley going around giving talks, posting on x etc saying “if you don’t learn this stuff you’re gonna be left behind”. I think this was around when he made the first Ralph blog post?
Which of course couldn’t be true. Any “prompt skill” is going to be commodified. Thats the entire premise AI companies are trying to sell.
100% agree with this, tooling is no longer an advantage.
The only thing I say to myself on this, given how Ralph took months to be notice (and taskmaster is still flying somehow under the radar comparatively speaking), is that people are drowning with the volume of new features / tools. It’s what you do with these tools that matters at the end of the day and shift goes more on GTM, marketing etc. rather than uniqueness of software. Most important thing: find clients :)
Anyway interesting times!
I am musing with the idea that other than dipping a toe in, investing a lot of time in this stuff is a waste (for this reason) and a better use is get deeper human domain experience in XYZ.
Agree, like I said in my other post reviewing what Jason Lemkin was doing with GTM: pick one tool, learn how to use it in real world scenarios, gain experience and you will be hyper employable.
It’s the application that matters imo
> Without proper task sequencing, agents kept stepping on each other. Which leads to the obvious question: what exactly does each tool give you?
In Gas Town, they “agent their way out” - it has a different type of worker that merges work and if needed can creatively rewrite completed work to suit the new state of a fast moving codebase.
So- sometimes even folks who build agent tools miss chances to take themselves out of the loop! But it’s one of the most powerful ways to scale yourself.
What both Ralph Loops and Taskmaster miss: Vetted planning processes to ensure you thought through all the details that need to be in the tasks. Did the plans generated by the tools think through all the security, data modeling, performance gaps, and so many other checklists of considerations?
If it's not baked in, the AI may be skipping over it. You'd have no idea until you run into something ugly.
Yes agree that’s why my PRD gets vetted by another agent before I even start breaking it down. Takes all dimensions you mentioned. Happy to share more about this if other are interested
Once, long ago, I was a fledgling C programmer working on the TinyMUCK game server. My mentor had released the 2.0 version with MUF, and I had implemented the port to SunOS (where a dereferenced NULL pointer does not return 0, but SIGSEGV: that was a lot of fun to debug!)
Later on I was working with another fellow to kind of bring the codebase up-to-date, and we found it necessary to implement a new database dump format (the database was normally 100% in RAM and then "dumped out" to a flat file for checkpoints and shutdowns.)
So I made the database changes, and then I christened the format "Christina Applegate TinyMUCK Dump Format" because she was the girl/woman of my dreams at that point in time (prior to Melissa Joan Hart taking over).
It is unclear if she ever found out about this particular usage. But last time I checked, this codebase was still extant, and so, someone somewhere may still be running a TinyMUCK server that utilizes a unique format dedicated to Christina Applegate herself.
The complexity aspect of the planning is one aspect I’d been missing. It fits nicely next to “list assumptions and then check them” and “finish one f#%^ing thing at a time” advice that I give to human teams which is also a struggle for agents.
> That’s usually how it goes. The practitioners find the patterns first. Then the patterns become features.
This is the scariest thing atm with the fast pacing of these things. As capabilities increase, everything you've spent time on building (w/ scaffolding, tooling, etc) gets "merged" into the all-you-can-prompt solution that the big labs provide. If your previous work has no differentiation, it's very hard to provide additional value / monetise it. And it's hard to know what will be differentiation or what will get eaten up.
It's that sci-fi story trope of the colony ship that gets overtaken by a new generation engine, and when they reach their planet they find a thriving colony there already. But with software :)
reply