Yeah they are pretty bad at it still, latest models tried to ship a basic SQL injection flaw.
Was also happy to build out an xss flawed module end-to-end.
Definitely have to keep a close eye on it.
My vibe code friends have pretty much infinite security issues.
Don't even have basic data modeling at client-server boundaries or anything.
Also had Google analytics embed that read and saved everyone's credit card details as clear text in analytics.
Seems to make pretty much infinite mistakes if you don't take care and tell it what not to do or how to build certain features.
I mean I'm not going to make a chrome extension and install it and update it every time hn changes or something breaks and update it and shit. For a site I often go years without looking at. I'll just be vaguely annoyed that a super popular website can't be bothered to add really basic usability features.
As a power user of Photoshop, I will say yes, most people use about 3-10 features that adobe offers.
But there are thousands of free tools for those people already, the point is this guy is saying he cloned the entirety of the adobe creative suite with vibe coding in a week.
That's not true. He made a bunch of simple and buggy "creative suite flavored" apps. That's a completely different thing than what he claims.
I tried the Photoshop one when they promoted it a few days ago here. I loaded up one of the client projects I'm working on right now and I could barely move the document or do anything it was so laggy and every single button/feature I tried to use had some kind of bug.
Maybe they've fixed everything in 2 days but I kind of doubt it.
What makes you think so?
It's not my experience, so I'd like to hear what kind of software you work with/teams and what is leading you to understand that code doesn't need review.
Might be the type of projects you are working on and how much you care about performance and code quality.
Working on more complex, logic heavy projects with strong performance needs I find the models to be useful but certainly not 'one shot' on pretty much anything. And often incredibly frustrating and genuinely bad code that collapses performance and bloats systems - like what a really bad junior might write.
When I'm working on large standard crud web projects with already decent architecture and a good harness and skills, honestly they work pretty well a lot of the times, the code looks good, does what it needs and fits in with the architectural style.
I really think a lot of hn people just write simple repetitive software, and a small portion works on complex, weird, dense, and novel'ish logic projects. The two obviously don't have the same experiences.
The original posters were better than any of the mockups.
Not because they looked good, but because they used a design language that "at-a-glance" said what the event was.
Sure, the designers republic/etc looked less commonplace, but if I was looking for a fun local faire I would absolutely never notice those posters and if I went i'd assume it was a completely different type of event than it is (e.g. some sort of modern art faire).
Every one of those posters didn't fit the medium idea at all (local faire event) except the child's drawing one could maybe pass.
In fact I can almost guarantee that all the posters in this article would perform worse than the originals if you were to test them on the street or in a facebook group.
If you are an actual production/commercial designer, your first goal is to understand what the clientele wants and converts, secondarily make it beautiful.
This failed both, zero understanding of the purpose of commercial art (to speak to the actual clientele and bring in more people) and ugly within their own design language (but yes, less common).
Would have been interesting to try and make designs that actually make sense for this product AND are a bit less generic.
my exact thoughts. i clicked on that fb post and someone in the comments linked their non-ai poster and i was just like, oh..that event seems way less exciting and fun and spring. i want to agree w the premise of the article but all the examples are worse and spark no desire in me to go to the fayre
I'd be pretty careful with this kind of thing. My friend vibe coded something similar and it had some very unexpected real world bugs like instantly locking the engine, cranking the engine to 100 in a second and burning the motor out, etc. So something like an escooter that you might ride across a busy road may not be the best use of vibe coding.
I just setup a large refactor with Astra and was feeling super lazy and let it mostly do it without my usual extreme micro managing.
The refactor ended up adding 22,000 loc.
I went in there and quickly read through it, laughed my ass off. Reverted the work tree. Micromanaged a new refactor. Net lines of code for something really elegant and easy to reason about was -3k loc in the project.
In case you are wondering why vibe coders are doing 30k loc a day, this is why.
My vibe code friends have pretty much infinite security issues. Don't even have basic data modeling at client-server boundaries or anything. Also had Google analytics embed that read and saved everyone's credit card details as clear text in analytics.
Seems to make pretty much infinite mistakes if you don't take care and tell it what not to do or how to build certain features.
reply