Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

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 Aufrufe • vor 1 Monat •via X (Twitter)

24 Kommentare

Profilbild von Peter Steinberger 🦞
Peter Steinberger 🦞vor 1 Monat

love this

Profilbild von Christopher Ehrlich
Christopher Ehrlichvor 1 Monat

hope not

Profilbild von Thorsten Ball
Thorsten Ballvor 1 Monat

Not AGI yet

Profilbild von Andrei Maxim
Andrei Maximvor 1 Monat

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.

Profilbild von Andreas @ Users & Groups
Andreas @ Users & Groupsvor 1 Monat

Blobware, when it outgrows everyone ;)

Profilbild von Alex Schüren
Alex Schürenvor 1 Monat

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 :(

Profilbild von Thomas Schranz 🍄
Thomas Schranz 🍄vor 1 Monat

team jellyware

Profilbild von MetaMike
MetaMikevor 1 Monat

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.

Profilbild von Pixygon
Pixygonvor 1 Monat

Maybe we should just skip straight to plasmaware!

Profilbild von Modibo Sissoko
Modibo Sissokovor 1 Monat

I am officially a Jelliware engineer!

Profilbild von Edu
Eduvor 1 Monat

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

Profilbild von Igor bedesqui
Igor bedesquivor 1 Monat

YESSSSS

Profilbild von 獨行俠 Kevin Tan (silverdemon101)
獨行俠 Kevin Tan (silverdemon101)vor 1 Monat

Jellyfish.

Profilbild von Nico Baier
Nico Baiervor 1 Monat

jorbs

Profilbild von Bryan Cinman
Bryan Cinmanvor 1 Monat

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

Profilbild von Mikkel Malmberg
Mikkel Malmbergvor 1 Monat

Reminds me a little bit of what @searls coined shovelware

Profilbild von Reece
Reecevor 1 Monat

Dario doppelganger saying some common sense

Profilbild von Robert Taylor
Robert Taylorvor 1 Monat

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

Profilbild von Will
Willvor 1 Monat

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

Profilbild von Ian Hsiao
Ian Hsiaovor 1 Monat

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

Profilbild von Daedelus
Daedelusvor 1 Monat

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

Profilbild von Fackler
Facklervor 1 Monat

i cant find a yt video demoing orbs.

Profilbild von Thorsten Ball
Thorsten Ballvor 1 Monat

Look at the time capsule:

Profilbild von Fackler
Facklervor 1 Monat

ty sir

Ähnliche Videos