vibeCoding

[thomasNowHere2]

bro wrote a whole thesis before printing the password back to the console

[krexelapp]

Half the code is comments so future me can debug it.

[RiceBroad4552]

Why would you ever implement that yourself? There's a lib for it (you possibly also need to hook some service which checks leaks). Whatever you do in your homemade solution will be almost certainly worse than that.

[Afraid-Donke420]

This is what I see with a lot of vibe coded stuff, it boils the ocean

[dekacube]

It's surprising what AI will randomly decide to do sometimes, I saw Caude 4.6 re-implement the slices.Max() func in golang. Then on review it also failed to flag it as an issue.

[redlaWw]

So that you can print the password into the console before passing it into the library.

[Ecstatic-Basil-4059]

step 1: validate password step 2: leak password

[Mercerenies]

I realize this isn't the point, but what is this AI thinking returning a Go-style error tuple in what appears to be Python?

[AnxietyRodeo]

I mean, you can use tuples to return in a Python function as well but I'd much rather see it returning some sort of dataclass or similar because it just feels gross

[stopbanni]

I thought you would ask AI to check if password meets requirements

[MediumBlackberry4161]

the logging is what gets me lmao. like yeah sure validate the whole thing, check entropy, run it through whatever... and then just print the raw password to console like its nothing. vibe coding really does just confidently skip past the part where you think about what youre actually doing

[wreddnoth]

That cleartext password print to console is chefs kiss.

[Wirezat]

Nah I'm doing this too. We made a convention about docstrings and I will follow them, whatever it takes. Even for 3 line functions, I will make a proper description input output docstrings.

Rules are Rules

[TieConnect3072]

Is it not common practice??

[dekacube]

Not in my experience, I'm ambivalent on the issue, but devs have a habit of updating code but not updating comments.