Git Blame is a pretty good alternative if you don't have delusions of changing the way your company writes code. To write explanation first, code second, requires a pretty sophisticated system that can't just be shoehorned into an existing culture or program. You also need a lot more money up front, because none of this is free even if you expect there could be losses in the future for maintainance. In my opinion, like uncle bob, appealing to students that they can tell their bosses what to do is foolish. Too much appeal to emotions, not enough research of the claims.
this is one of the most valuable talks i even seen. thank you
What fields are you into? school/work?
Gee, what a great talk! This guy is both knowledgeable and funny! :-)
This is such a great talk
Anyone know where we can find the slides?
This is why Lions was such a popular book en.wikipedia.org/wiki/A_Commentary_on_the_UNIX_Operating_System it made Unix literate!
So true, so very very true! Listen to this guy ...
Words of wisdom.
Links would have been great.
Git Blame is a pretty good alternative if you don't have delusions of changing the way your company writes code. To write explanation first, code second, requires a pretty sophisticated system that can't just be shoehorned into an existing culture or program. You also need a lot more money up front, because none of this is free even if you expect there could be losses in the future for maintainance. In my opinion, like uncle bob, appealing to students that they can tell their bosses what to do is foolish. Too much appeal to emotions, not enough research of the claims.