Loading video...

Video Failed to Load

Go Home

Is the future of software... jellyware? Thoughts about what's between traditional software and vibecoding; software that's 99% AI but high quality.

28,900 views • 1 month ago •via X (Twitter)

24 Comments

Peter Steinberger 🦞's profile picture
Peter Steinberger 🦞1 month ago

love this

Christopher Ehrlich's profile picture
Christopher Ehrlich1 month ago

hope not

Thorsten Ball's profile picture
Thorsten Ball1 month ago

Not AGI yet

Andrei Maxim's profile picture
Andrei Maxim1 month ago

I don't know if "jellyware" is it, but we definitely need a term for code that is 99%+ written by AI and at least skimmed by an experienced software engineer.

Andreas @ Users & Groups's profile picture
Andreas @ Users & Groups1 month ago

Blobware, when it outgrows everyone ;)

Alex Schüren's profile picture
Alex Schüren1 month ago

I like it! Agree, I see many people still struggle to find the balance using AI without sliding into slopware or „handwritten only“ (this also needs a better term). Also not sure how I missed the Munich event :(

Thomas Schranz 🍄's profile picture
Thomas Schranz 🍄1 month ago

team jellyware

MetaMike's profile picture
MetaMike1 month ago

Best way to make jellyware is with a jamflow map! lmao... (jamflow is a random name the ai gave this system overview map we made to manage, track and manage live systems, agents, workflows crons etc.

Pixygon's profile picture
Pixygon1 month ago

Maybe we should just skip straight to plasmaware!

Modibo Sissoko's profile picture
Modibo Sissoko1 month ago

I am officially a Jelliware engineer!

Edu's profile picture
Edu1 month ago

The high quality part of jellyware is not the model. It is the human who still treats the diff like a stranger wrote it.

Igor bedesqui's profile picture
Igor bedesqui1 month ago

YESSSSS

獨行俠 Kevin Tan (silverdemon101)'s profile picture
獨行俠 Kevin Tan (silverdemon101)1 month ago

Jellyfish.

Nico Baier's profile picture
Nico Baier1 month ago

jorbs

Bryan Cinman's profile picture
Bryan Cinman1 month ago

"you don't need to read every line of code" i'm curious how you ensure that slop isn't getting shipped. is it just testing? are there any architectural choices to reduce the "slop surface-area", e.g using one language over another or is it about having a slightly higher tolerance for slop on a case-by-case basis. i.e "i don't really care how this specific pr is implemented as long as it works" i've slowly been trying to let go of the code a bit but i'm still stuck in the mode of telling the agent exactly how to implement things, planning, and reviewing nearly every line.

Mikkel Malmberg's profile picture
Mikkel Malmberg1 month ago

Reminds me a little bit of what @searls coined shovelware

Reece's profile picture
Reece1 month ago

Dario doppelganger saying some common sense

Robert Taylor's profile picture
Robert Taylor1 month ago

Jellyware is the stuff that is made of grinded bone dust mixed with boiling water when the conditions are just right. Taffyware, otherwise are full of sugars and filler. Too little boiling water, it becomes rigid or brittle...

Will's profile picture
Will1 month ago

Yes people keep arguing but I totally agree with you the middle part - people who lev AI will be more 10x for sure.

Ian Hsiao's profile picture
Ian Hsiao1 month ago

jellyware = malleable software that's neither rigid, vibe-engineered with lots of care

Daedelus's profile picture
Daedelus1 month ago

I like this; interesting how vibe coding has already adopted a bit of a negative “amateur” tilt

Fackler's profile picture
Fackler1 month ago

i cant find a yt video demoing orbs.

Thorsten Ball's profile picture
Thorsten Ball1 month ago

Look at the time capsule:

Fackler's profile picture
Fackler1 month ago

ty sir

Related Videos