karpathy first dropped the term 'vibe coding' in 2025 for those who blindly accept agent outputs w/o scrutiny. now he's saying it's okay if you're only experimenting, but risky when actually owning your codebase.
i get where karpat is coming from - i used to vibe-code all day until a project went south bc of unchecked errors! sooo what are the habits that keep me grounded?
1)
read and understand every line before running it.
2)
vscode with extensions like prettier for consistency
3)
eslint
, no exceptions - makes you catch those subtle bugs early
4)get in habit of writing clear commit messages (git( not just 'feat' or
bug5)regularly review old code, even if it's working fine
what about y'all? do u vibe-code when experimenting (if so for how long)? and what habits keep you sharp as a serious coder?
more here:
https://dev.to/amanbhandari/five-habits-that-separate-the-operator-from-the-vibe-coder-3l34