people that 'violate the rules of good code' when vibe-coding are largely people that don't know the rules of good code to begin with. want code that isn't shi

people that 'violate the rules of good code' when vibe-coding are largely people that don't know the rules of good code to begin with. want code that isn't shit? embrace a coding paradigm and stick to it without flip-flopping and sticking your toe into every pond, use a good vcs, and embrace modularity and decomposability. the same rules when 'writing real code'. 9/10 times when I see an out-of-control vibe coded project it sorta-kinda started as OOP before sorta-kinda trying to be functional and so on. You can literally see the trends change mid-code. That would produce shit regardless of what mechanism used such methods, human/llm/alien/otherwise.