I've used it to create little one-off tools that I needed for some specific tasks, without any care whether it's "of substance" or "investable." In the past, I might have Googled around to see if there was an existing app or open-source package to do the job. Quite often, the AI agent will use some existing software packages, but I didn't have to find them and figure out how to use them.
A real example from today: I got tired of the Looney Tunes way-too-colourful screensaver options on my Mac mini, so I asked Claude how to get a screensaver that is a nearly-black uniform monochrome grey. Surprisingly, that's not actually an option in macOS System Settings. So Claude just wrote a little Python script to generate the images I need for my two displays, saving them to the right place on my Mac mini. It used the Pillow package, but I didn't have to spin up a whole Python project and install Pillow; it just used PEP 723 inline script metadata to tell uv to use Python >=3.12 and to install Pillow. Then Claude gave me the uv one-liner to run the script (uv run ~/make_screensaver.py) and instructions for how to tell my Mac mini to use the generated files. The whole process took about 15 minutes from when I started writing the first prompt to the time I had my new screensaver working.
I think vibecoding itself is the substance. Like enabling people who don't have software engineering or code writing experience to actually develop software is a value in itself. I don't think there needs to be any other proof of concept than a layman can hop on to lovable base 44. Intermediates can grab cursor and Claude Code and just rip through potential project lists to test things out and see where they could go. I guess my opinion is the tool is the product in this case. Most canvases that get sold don't go to professional artists; they go to amateurs. That's mostly what the canvas market is comprised of: people who want to be artists, though they'll never sell a painting.
I've used it to create little one-off tools that I needed for some specific tasks, without any care whether it's "of substance" or "investable." In the past, I might have Googled around to see if there was an existing app or open-source package to do the job. Quite often, the AI agent will use some existing software packages, but I didn't have to find them and figure out how to use them.
A real example from today: I got tired of the Looney Tunes way-too-colourful screensaver options on my Mac mini, so I asked Claude how to get a screensaver that is a nearly-black uniform monochrome grey. Surprisingly, that's not actually an option in macOS System Settings. So Claude just wrote a little Python script to generate the images I need for my two displays, saving them to the right place on my Mac mini. It used the Pillow package, but I didn't have to spin up a whole Python project and install Pillow; it just used PEP 723 inline script metadata to tell uv to use Python >=3.12 and to install Pillow. Then Claude gave me the uv one-liner to run the script (uv run ~/make_screensaver.py) and instructions for how to tell my Mac mini to use the generated files. The whole process took about 15 minutes from when I started writing the first prompt to the time I had my new screensaver working.
Claude Code itself. Boris himself has said that they use Claude code to build Claude code and have been doing so since late last year.
I think vibecoding itself is the substance. Like enabling people who don't have software engineering or code writing experience to actually develop software is a value in itself. I don't think there needs to be any other proof of concept than a layman can hop on to lovable base 44. Intermediates can grab cursor and Claude Code and just rip through potential project lists to test things out and see where they could go. I guess my opinion is the tool is the product in this case. Most canvases that get sold don't go to professional artists; they go to amateurs. That's mostly what the canvas market is comprised of: people who want to be artists, though they'll never sell a painting.
Anthropic wouldn't be anthropic with claude. Most engineers now actively use it to build, myself included. I design and build our actively with it.
Are you trying not to sound like AI by cutting half your sentences? Either way.. Anthropic is Anthropic because of Claude
Claude code is pretty good for coding compared to others in my personal opinion. It to me feels a really good fit for vibe coding.