No transcript available for this episode.
Developers are cracking. And it is not because they work too much.
In barely a year, artificial intelligence has invaded our offices with a brutality nobody had really foreseen. ChatGPT, Claude, DeepSeek… these tools have become our new reflex, our universal shortcut, our constant validation.
But something is cracking. The first to fall are not novices lost in front of technology. They are seasoned engineers, ten or fifteen years in the job, who used AI as an accelerator. Their diagnosis is unanimous: cognitive exhaustion, loss of meaning, silent burnout.
This phenomenon has a name: vibe coding. And it is not only about developers.
Because what these professionals are going through with code today, we are already going through with our emails, our reports, our strategies. Zero friction is not liberation. It is a spring-loaded trap.
95% of companies see no measurable return on their generative AI investments. We produce more. We create less value. And meanwhile, something far more precious is quietly eroding: our ability to think for ourselves.
Here I explore why the real question is not “how to use AI better” but a far more uncomfortable one: what are we becoming while we use it?
Find the full transcript of this episode, along with all the sources and plenty more, at: From vibe coding to vibe thinking: when ease becomes a trap