There's a new kind of coding I call "vibe coding", where you fully give in to the vibes, embrace exponentials, and forget that the code even exists. It's possible because the LLMs (e.g. Cursor Composer w Sonnet) are getting too good. Also I just talk to Composer with SuperWhisper so I barely even touch the keyboard. I ask for the dumbest things like "decrease the padding on the sidebar by half" because I'm too lazy to find it. I "Accept All" always, I don't read the diffs anymore. When I get error messages I just copy paste them in with no comment, usually that fixes it. The code grows beyond my usual comprehension, I'd have to really read through it for a while. Sometimes the LLMs can't fix a bug so I just work around it or ask for random changes until it goes away. It's not too bad for throwaway weekend projects, but still quite amusing. I'm building a project or webapp, but it's not really coding - I just see stuff, say stuff, run stuff, and copy paste stuff, and it mostly works.

Very few in the bureaucracy actually work the weekend, so it’s like the opposing team just leaves the field for 2 days! Working the weekend is a superpower 😂

🚨 New @a16z thesis - an update on AI voice agents! 2024 was a huge year for voice agents, with massive model breakthroughs + hundreds of new startups. How has the space evolved, and where do we see opportunity in 2025? Our update + market maps for B2B and B2C 👇

Most people wait too long to go into action, generally out of fear. They want more money or better circumstances. You must go the opposite direction and move before you think you are ready. It is as if you are making it a little more difficult for yourself, deliberately creating obstacles in your path. But it is a law of power that your energy will always rise to the appropriate level. When you feel you must work harder to get to your goal because you are not quite prepared, you are more alert and inventive. This venture has to succeed so it will.

Have been playing with OpenAI's "Operator" agent all weekend. Some early thoughts: 1) The fact that it's already hosted and you can just start using it means it'll be more widely used than Claude's "Computer Use" feature. 2) Operator will be able to make websites that haven't had APIs available (for whatever reason) behave as if they did. They'll now be automatable. 3) Operator is a bit like tool calling in LLMs. Except it uses the entire Internet as its set of "tools" (whether the site has an API or not). 4) We might see a form of caching/pre-compiling for widely used functions. Essentially, Operator could write its *own* API for things that are commonly needed, and then just use that to get that particular task done. 5) Operator can use itself behind the scenes to distribute a long list of tasks across multiple instances of a virtual browser. 6) Operator will likely be able to reason through how a task could be parallelized. Example: Task involves paging through 50 web pages of results. Instead, it could say: Operator A will start at 1st page and go forward. Operator B will start at last page and go backwards. They'll "meet in the middle" when all pages are done. 7) Current websites were (mostly) built for humans and APIs were (mostly) built for developers (a special type of human). Mobile sites were built for humans using mobile devices. I wonder if we'll see websites created specifically for use by agent AIs. Anyone else enamored with Operator yet? What kinds of use cases are you trying it out on?