I think the point is that if you just browse a code base to learn you lose much of the timing information. Even if you examine the commits you can't really predict how much time it took to make a certain change and most though process is probably lost. Also it's common to squash smaller commits before push so it makes one, but consistent commit.
I don't argue if there is any value in this, but there is certainly plus information following the thought process of a programmer. The parts that takes longer to write emphasize harder and more thought out modifications for example.
>Unlike Twitch, Livecoding automatically archives every stream, which means that it’s quickly accumulating an extensive video library — although, right now, it’s not terribly well organized.
Organize live sessions by commit somehow. I guess only open source developers stream anyway (I couldn't try the site, I don't have Flash) and if they could easily or even somewhat automatized could tag live sessions or parts of live sessions by commit hash it would be really nice. Imagine browsing a codebase in git, looking at some seemingly odd code and thinking "what was the thought process of the guy who wrote this?". Then you make a git blame, then enter the commit hash to search on livecoding, maybe the guy has the session up there and you can get more info.
I don't argue if there is any value in this, but there is certainly plus information following the thought process of a programmer. The parts that takes longer to write emphasize harder and more thought out modifications for example.
>Unlike Twitch, Livecoding automatically archives every stream, which means that it’s quickly accumulating an extensive video library — although, right now, it’s not terribly well organized.
Organize live sessions by commit somehow. I guess only open source developers stream anyway (I couldn't try the site, I don't have Flash) and if they could easily or even somewhat automatized could tag live sessions or parts of live sessions by commit hash it would be really nice. Imagine browsing a codebase in git, looking at some seemingly odd code and thinking "what was the thought process of the guy who wrote this?". Then you make a git blame, then enter the commit hash to search on livecoding, maybe the guy has the session up there and you can get more info.