(www.wiz.io)

122 points waldopat | 1 comments | 30 Jul 25 16:12 UTC | HN request time: 0s | source

Show context

zamalek ◴[30 Jul 25 17:09 UTC] No.44736778[source]▶

Hot on the wheels on the vibe-coded Tea breach. Things are looking great for vibe coding.

Don't get me wrong, I have been been more hands off (though not completely, and very prescriptive) with an SPA side project and it's going great. Claude makes way better looking UIs than my dog ugly developer UIs. But vibing auth? That should seriously count as _legal_ gross negligence.

replies(5): >>44736996 #>>44737543 #>>44737655 #>>44738035 #>>44738150 #

sunaookami ◴[30 Jul 25 18:45 UTC] No.44738035[source]▶

>>44736778 #

The Tea breach was not due to vibe-coding btw, the code was from the beginning of 2024 when vibe coding wasn't even possible.

replies(4): >>44739256 #>>44740066 #>>44740077 #>>44741548 #

1. QuadmasterXLII ◴[31 Jul 25 01:46 UTC] No.44741548[source]▶

>>44738035 #

Vibe coding started working in summer 2023, see e.g. https://github.com/HastingsGreer/jstreb/blob/1ccedf82ec463dc...

the spectacular overcommenting has been here the whole time

Progress since then has mostly been people and tools catching up to the models, the limit of what the models can code has been pretty stagnant the last couple years

↑

Critical vulnerability in AI coding platform Base44 allowing unauthorized access