pull down to refresh

100 sats \ 1 reply \ @Scoresby 8 Oct \ on: Vibe Tools, Not Apps builders
I have a hard time thinking about this in the context of apps and tools, so I'm going to abuse my powers of analogy and compare it to writing.
Using AI to produce writing might be useful/interesting if you requested the information from the AI. Presumably, you asked a question you thought it would be faster at answering than other means of getting an answer, and you want the information it will provide.
Posting AI writing with the expectation that other people will read it or find it interesting is almost always a waste of time, because they could simply ask AI for the information themselves, in the way that best suits them.
AI writing that answers your unique question is valuable.
AI writing that answers other people's questions is not as valuable.
write
preview
0 sats \ 0 replies \ @optimism OP 8 Oct
Right. I think that I have 2 assertions on top of this that leads to tools not apps:
  1. Apps constrain whereas tools liberate, Justin gave us a delightful anecdote. Also think about Jack saying "Twitter should have been a protocol, not an app". This is a variation of the "apps constrain" view.
  2. k00b made a good argument for pain-driven development. The most immediate feedback on the product of your work is the reduction of your own friction.
There is an additional assertion why I don't say frameworks/protocols, not apps like Jack, because I'm talking in the pure context of vibe coding, not "real" coding like a pro. The productization of vibe coded slop is much more cumbersome than the slower process of writing precision code and the net benefit over time negligible to non-existent. The main issue you'll have as a non-coder, even if the bot would write non-sloppy, concise code, is that you don't understand it, and thus you don't understand the mistakes the bot makes. The bot definitely makes mistakes; all the time. Thinking that it doesn't is a feature of your ignorance, not the bot's perfection.
Because of this, the best possible outcome of a vibe coded product is bespoke automation in your workflows. You will not only feel immediate relief, but you also immediately feel the pain if there is something off. You can act quickly and decisively; you don't need democracy in your own tools.
Bottom line, I'm advocating something non-consensus here: personal efficiency is the highest good, because it makes you less reliant on others and helps you focus on exercising mutually beneficial relations rather than dependent ones. Dependency works counter-efficient, at least that is what I believe as a freedom maxi.
reply