←back to thread

122 points waldopat | 2 comments | | HN request time: 0.451s | source
Show context
zamalek ◴[] 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 ◴[] No.44738035[source]
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 #
bluefirebrand ◴[] No.44740077[source]
Just because no one had coined the term vibe coding yet doesn't mean people weren't trying what would eventually be called vibe coding

We had LLMs in 2024 that you could certainly try vibe coding with, but probably shouldn't have

Just like we have LLMs today that you can certainly try vibe coding with but probably shouldn't

replies(1): >>44741520 #
1. cwmoore ◴[] No.44741520[source]
Wasn’t that default public-accessible Firebase?
replies(1): >>44742234 #
2. sunaookami ◴[] No.44742234[source]
Yes which is why the other comments don't make any sense because everyone just reads headlines.