Why Some Developers Are Live-Streaming Their Coding Sessions

itwbennett writes Adam Wulf recently spent two weeks live-streaming himself writing every line of code for a new mobile app. He originally started to live-stream as 'a fun way to introduce the code to the community.' But he quickly learned that it helps him to think differently than when he was coding without the camera on. "Usually when I work, so much of my thought process is internal monologue," he said, "but with live streaming I try to narrate my thought process out loud. This has forced me to think through problems a little differently than I otherwise would, which has been really beneficial for me."

Comments

Rubber Ducking

[booch]

It's called Rubber Ducking. The idea is that by talking out loud, you have to form your thoughts into words, which requires you to organize your thoughts more completely. Think about all the times that you've gone to ask someone a question, and as soon as you ask them the question, you figure out the answer yourself. Whether you use a rubber duck, a live video audience, or another person doesn't matter much. This is one of the reasons that pair programming can be quite effective.