Sort of a PHP-like, folder based web serving tool that executes Javascript. Very quick and fluid.
552 karma · joined September 10, 2014
Sort of a PHP-like, folder based web serving tool that executes Javascript. Very quick and fluid.
There is no doubt in my mind that he is personally pissed because Anthropic stood up to him.
Now I have a favorite in my bookmark bar for each project I am working on that shows me the docs.
I'm so happy.
The endpoint verifies that the destination specified by the POST is in my project folder. If it points at an existing file, it creates a version. It does not overwrite.
I added a CLI, watchFile, that blocks Claude until the file shows up.
And made a skill that tells Claude to respond nicely to "Make an interactive document that...".
Claude Code has basically made software functionality, "Your wishes come true".
I run a web server on my Mac. Consequently, I have an HTTP process available. I keep intending to make an endpoint that Claude can use. I would tell it to make a document for commenting (or put a list of options or whatever) and post it to, I guess, the planning folder we are working in. The endpoint would know how to do this because I wrote it.
When it gets there, I would, I wanted to keep it, tell Claude to integrate the results into the file as static HTML. Or, if I don't care about that, just read it and do whatever I said and leave it disconnected.. The goal isn't to make a website.
This supports interactive conversations with Claude via HTML.
BUT, I only do this as an easy way of referencing specific ideas and text in notes to instruct Claude. I say, "I have added notes. Read them and adjust the doc accordingly." Or, "Read the notes I added. Turn them into html."
It's an insanely productive pattern.
Generating markdown is faster so unlike our friend here, I still do use it for straightforward things.
BUT, in general, I tell Claude, "I think we should starting a project planning folder for this. Put (the stuff we just talked about) into an html doc. while you're at it, make an index.html and put relative link to the page with a little explanation of what we are up to."
Or, just yesterday Claude and I worked out the design for a substantial AI enabled database tool. I had it make an explanatory doc for my team. It was a single html file that navigated through forty scenes that demonstrated it. MAGIC.
If you aren't doing your collaboration with Claude in html, listen to this guy. Your life and work will be better.
In practice, most designers know what they are doing as well as you know your job. If yours doesn't, you hired a quack.
Here. Try this, in practice, most business owners don't know what they are doing. In practice, most programmers write shit. It's easy to bitch at artists because most people don't understand what they do. Don't be one of those people.
I am 100% supportive of it being used for training... AI, you, everyone.
It has basically eliminated surprises like that.
Hasn't happened in a long time. Opus 4.6 is a miracle improvement.
It has examples of all the parts of a web app written, over many years, to be my own ideal structure. When the LLM era arrived, I added a ton of comments explaining what, why and how.
It turns out to serves as a sort of seed crystal for decent code. Though, if I do not remind it to mimic that architecture, it sometimes doesn't and that's very weird.
Still, that's a tip I suggest. Give it examples of good code that are commented to explain why its good.
I suppose if you are doing something that truly can be decided based on a test but, I just don't see it, at least for anything I do.
You have to figure out what you want before the AI codes. The thinking BEFORE is the entire game.
Though I will also say that I use Claude for working out designs a lot. Literally hours sometimes with long periods of me thinking it through.
And I still get a ton more done and often use tech that I would never have approached before these glory days.
I do a ton of programming but I also use it to learn all kinds of stuff. I'm into physics, history and philosophy and have done wonderful explorations.
Now I tell it what I had for breakfast just to see what it says. Half the time it says something interesting and I end up exploring another new thing.
"My people" for sure and everyone is mad at me because I think that.
Also, I don't care what they think. I am all about the fun.
Having an infinitely patient, super smart colleague available all the time is amazing.
I use NodeJS with a highly structured ExpressJS app for the API. It uses an npm module, tools-library-dot-d to implement a carefully scooped plugin structure for endpoints, data model and data mapping. It has built-in authentication and database (sqlite).
Nuxt/Vue/Vuetify/Pinia for the UI. It has a few components that implement things (like navigation) the way I like. It supports login and user editing.
The stack includes a utility that looks at a directory for executable CLI tools (usually NodeJS or BASH) and adds them to the session PATH. The API stack has boilerplate to treat CLI apps as data-model services.
Does that help?
I'm having more fun than I've had in years.
Your description of the experience tells me that you have not figured out how to do it correctly.
I NEVER have bad experiences like that. I absolutely DO create production grade software reliably every day.
Treat it as collaborator instead of as a servant. You will get much better results.
You don't have any choice. Good or bad. It's here. Get over it.
I know that back in the day, people said automobiles were bad and evil and costing the buggywhip makers their jobs. Unfortunately for them, the decision to use cars had already been made.
I do AI with fervor because I live in the real world and the decision has already been made. You can't stop AI by pretending it's optional.
Adapt or die.
The people who are pained by AI subsuming something they do forget that it empowers them to do a million other things.