Here is one of my (written by I) favorites silly jokes to tell:
I just bought a do it yourself boat kit from Amazon.
wait to build tension
Just need to add water.
Here is one of my (written by I) favorites silly jokes to tell:
I just bought a do it yourself boat kit from Amazon.
wait to build tension
Just need to add water.
Put that on the landing page.
Your comment gave me a nightmare of that returning, but in AI form somehow.
It happened to compilers, operating systems, and renderer. It's gradually happening to game engines.
That's why the largest software companies are really just network effect monopolies. You only use it because other people use it or it relies on some sort of proprietary format.
Many companies like Adobe, Microsoft and Google could sustain a dramatically lower headcount if they started from scratch and never went outside the confines of their network monopoly markets.
From that perspective a one person unicorn is very feasible if we think about it as building a network effect monopoly.
In fact a close example already exists -- Minecraft was very close to being a single person unicorn.
If we have a one person unicorn, I'd imagine it'd be something more like Minecraft than someones newsletter or Google!
Will there be a shovel that uncovers a billion dollar gold nugget? Why sell the shovel then?
---
The idea is that convo files will serve as decencies of target outputs and those outputs could be anything from React components to generated images or videos.
---
This should make for a declarative way of defining generated application and content in a way that is repeatable and easy to modify.
---
I'll implement the same caching strategy that `make` uses to minimize the number of tokens consumed as changes to convo files are made.
---
Anybody have any thoughts or suggestions?