The Psychology of Bad Code: What Is Vibe Coding?
-
The Psychology of Bad Code: What Is Vibe Coding? And Why Developers Do It.
https://twp.ai/E6GjjZAI coding assistants are changing how we build software, but they’re also changing how we make decisions.
1/3 -
The Psychology of Bad Code: What Is Vibe Coding? And Why Developers Do It.
https://twp.ai/E6GjjZAI coding assistants are changing how we build software, but they’re also changing how we make decisions.
1/3In this video, Tanya Janca explains “vibe coding” — the very human tendency to accept AI-generated code because it looks correct, compiles cleanly, and helps us move faster. Developers aren’t careless. We’re responding exactly how humans respond to confident tools and tight deadlines.
2/3 -
In this video, Tanya Janca explains “vibe coding” — the very human tendency to accept AI-generated code because it looks correct, compiles cleanly, and helps us move faster. Developers aren’t careless. We’re responding exactly how humans respond to confident tools and tight deadlines.
2/3The real risk is not using AI. It’s quietly handing over our judgment without realizing it.
Understanding this shift is the first step toward building safer software in an AI-assisted world.
3/3 -
The real risk is not using AI. It’s quietly handing over our judgment without realizing it.
Understanding this shift is the first step toward building safer software in an AI-assisted world.
3/3@SheHacksPurple Muhaha. As if most people are willing to understand anything about themselves.
-
The Psychology of Bad Code: What Is Vibe Coding? And Why Developers Do It.
https://twp.ai/E6GjjZAI coding assistants are changing how we build software, but they’re also changing how we make decisions.
1/3@SheHacksPurple This comment is not related to your clip necessarily, which I entirely agree with, it just made me think of the following:
I keep drawing mental lines between 'vibe coding' and AI coding assistants (basically the second is still kind of working alongside you in some fashion like in an IDE, where the first seems like an extreme end of the spectrum with a funny name).
"Make me a CRM!"
It almost explicitly acknowledges its own unseriousness as a formal dev process designed to create production ready outcomes. I see many folks using it for prototyping or super MVP type stuff (that they nonetheless sometimes release in the wild).
I can't decide if those distinctions are actually meaningful though.
-
R AodeRelay shared this topic