Iterative Incremental #3 - Vibe Coding: My First Reaction and the Reasoning Behind It

カートのアイテムが多すぎます

ご購入は五十タイトルがカートに入っている場合のみです。

カートに追加できませんでした。

しばらく経ってから再度お試しください。

ウィッシュリストに追加できませんでした。

しばらく経ってから再度お試しください。

ほしい物リストの削除に失敗しました。

しばらく経ってから再度お試しください。

ポッドキャストのフォローに失敗しました

ポッドキャストのフォロー解除に失敗しました

Iterative Incremental #3 - Vibe Coding: My First Reaction and the Reasoning Behind It

無料で聴く

ポッドキャストの詳細を見る

When vibe coding went mainstream, my first reaction wasn't panic. It was curiosity. Then came a sharper question. The speed never bothered me. What bothered me was that not understanding the generated code had become part of the workflow, something you were supposed to accept.
In this episode I talk through how I reasoned about it, based on years of XP and DevOps. TDD, refactoring and continuous delivery aren't rituals to skip: they're the brakes that make speed safe. Vibe coding takes out the understanding loop that comes before the tests. Public incidents showed what happens when understanding is treated as optional at the moments it matters most. This isn't an ideological stance against AI. I'm against using AI without discipline, and I wanted AI to help me carry the cost of discipline instead of skipping it.

Follow & subscribe

Connect on LinkedIn for the ongoing conversation and the reflections that don't make it into an episode:
https://www.linkedin.com/in/daniele-scillia/

One framework or practice per week, straight to your inbox — subscribe to the newsletter:
https://learnagilepractices.substack.com/subscribe

まだレビューはありません