2026-10-09 04:14 UTC
The answers you’ve already gotten are the best. Commit patterns. By far.
But the code itself has a distinct shape: impeccable application of pattern. Essentially perfect.
Which then is juxtaposed by bizzare, compounding, and amplifying design choices, as if some invisible rule or assumption was invented and became a self imposed constraint to be worked around… with every iteration pointing at the previous as justification for it’s correctness for applying it the next.
Neither in isolation is weird, it’s the marriage of the two. It’d be like watching a pro driver making millisecond perfect RPM matching shifts and then struggle to parallel park. Like… It doesn’t make sense. It doesn’t appear in nature.
It’s normal to see a gap for human devs, although it’s typically inverted (better evidence of justification rational design choices, worse application of patterns). But it’s the MAGNITUDE of that gap (and ALWAYS favoring application of pattern) that gives it away.
Sufficiently supervised processes raise the level of design coherence to roughly that of the operator. So I’m sure I could be bamboozled in those cases. Not sure exactly sure how everyone draws the line for what constitutes “vibe-coding”.
Those are almost scarier though, because the level of QA or user testing would sit at non existent I’m sure.
Replies (0)
No replies.