Comment on Self-Host Weekly (2 October 2026)

• JustEnoughDucks@slrpnk.net ⁨2⁩ ⁨weeks⁩ ago

  Look at the code and commit history and/or talk to the developer.

  If the developer only commits in giant blocks of 1-2 days and mostly in a few hours and changes thousands of lines of code in that time, the chances of it not being vibe coded and actually being checked are extremely slim, outside of a complete project refactor. It used to be that LLMs would just do massive single commits, but now they do a thousand tiny commits on the same day using a ton of barely human-readable jargon (for less experienced devs) in the git commits.

  If the project was started past 2025 and the initial commit(s) on the first day were massive, that also points (less strongly) towards vibe coding.

  If the Dev can’t explain what his code does without having an LLM write the response (this is getting to be harder), that also generally also means that it was vibe coded.

  If the dev’s commit history only includes documentation, issues, or very very small things until 2025-2026 and combined with one of the above, it is usually vibe coded.

  The vibe coding identifying sites online are complete garbage with mostly false positives. For example, if I run it on my old github repos from before LLM coding existed, it says that it is very likely vibe coded because I comment a ton because my memory isn’t great and I am an electronics guy with very bad coding git management so my git commit history is like one or two commits per day when I am working on something, but I try to bullet list all of my changes in a readable way for people not familiar with the code (like myself in 1 year lol)

  source

  • prenatal_confusion@feddit.org ⁨2⁩ ⁨weeks⁩ ago

    Thanks for your reply

    source