Max Shaw
Verified account Windmill@_maxdshaw
834 Following 515 Followers 1.1K Posts
Latest posts 5
Today Windmill has
@_nicolealonso running 100km
@emyang___ running 26 miles
And I might run 3 on the treadmill watching football.
What a day for peak performance
@_nicolealonso running 100km
@emyang___ running 26 miles
And I might run 3 on the treadmill watching football.
What a day for peak performance
100 km and 15.5 consecutive hours later… @_nicolealonso finished!View quoted post on X
The more feedback you can get flowing in to your product the better.
I wouldn't recommend fully automating the build process unless the app is just for you but you need a fast loop from feedback -> improvement. We always have a human in the loop to make sure we are building the right thing.
For feedback we use a combination of a bunch of methods:
* Users can leave feedback via our agent
* Users can leave feedback in the platform
* Our agent can leave feedback based on self reflection
* We have simulated user feedback agents which send in feedback.
I wouldn't recommend fully automating the build process unless the app is just for you but you need a fast loop from feedback -> improvement. We always have a human in the loop to make sure we are building the right thing.
For feedback we use a combination of a bunch of methods:
* Users can leave feedback via our agent
* Users can leave feedback in the platform
* Our agent can leave feedback based on self reflection
* We have simulated user feedback agents which send in feedback.
I'm now building an "improvements" feature into all of my personal vibecoded applications: a freeform text input that's hooked up to an agent that yolo implements whatever is submitted.
It's an interesting experience -- the activation energy barrier to sanding any rough edge or implementing any new feature becomes extremely low. Someone else who uses one of the applications I created has already implemented 150 improvements over the course of a few days. This pattern feels like a new kind of tool -- liquid software? -- and every application that doesn't have this feature now has a slightly rigid and anachronistic flavor. Why can't I just tell it how I want it to be different?
Now, it's not obvious to me how this pattern can or should scale. Does it become unmaintainable after a while? (Maybe model intelligence improvement outstrips my feature appetite such that it's fine?) How does collaborative software work in this model? Can software designed this way be secure and reliable?
Whatever the larger questions about broader deployment, it definitely works great in a personal context. It reminds me a little of the visions of Lisp/Lisp machines, Smalltalk, and HyperCard -- systems that the user can take control of and modify. Those visions never quite worked, though: the vast majority of software today is not end-user modifiable in any useful way. So, while this "liquid" affordance is a very small touch, the way it changes one's relation to the software feels a bit transgressive and empowering in a Lickliderian and Engelbartian way.View quoted post on X
@WisprFlow Is this expected? I've barely used it this week. Is this a new limit?
@granola whats your limit?
@granola whats your limit?
If you don't have a full send skill you aren't gonna make it.