3 ms·
If you're writing CSS I suppose you can vibe code, but it won't work for anything more complicated. They get you close most of the time but you still have to wo
by esafak 2y ago
If you're writing CSS I suppose you can vibe code, but it won't work for anything more complicated. They get you close most of the time but you still have to work.
- lxgr 2y agoI've definitely implemented small utilities entirely in Claude (as webapps/"artifacts").
- williamcotton 2y agoI’ve had a lot of success with the method: https://github.com/williamcotton/search-input-query https://github.com/williamcotton/search-input-query Search box DSL with React component with syntax highlighting, error syntax reporting, etc. Converts AST to postgres ilike, tsvector or pg_search. https://github.com/williamcotton/guish https://github.com/williamcotton/guish A bi-directional GUI editor for constructing Unix pipelines with bash CLI parsed to graphical modules. All of these were made basically with the same tools and methods that Karpathy is describing as Vibe Coding. These are not just simple little projects. This approach is not just limited to making a few CSS changes.
- sublinear 2y agoI don't get how this sentiment still persists. This is simply not true if you're working on more serious websites for clients who actually audit for accessibility or responsive design, nor if you want it to be maintainable by web devs that actually know what they're doing. CSS definitely isn't as messy some C++ still out there in the wild. If you're doing it right you should be able to quickly write a minimal amount of code that does what you want even for fairly large websites. Involving AI for something so trivial would just get in the way. Bad CSS is usually due to the requirements specifying a terrible design, much like how bad requirements drive bad code in any other language.