I am thinking more of a high-level architecture overview by the team lead. IMO, a 1-hour whiteboard talk, done every 4-6 months, would be of genuine value.
It wouldn't help with specific corners of the code, but it would help to understand the culture. In a comment, Alex Miller mentions that Terracotta records design reviews (though they aren't viewed often) -- http://bit.ly/eoN1R4 On Feb 1, 4:55 am, "Vince O'Sullivan" <[email protected]> wrote: > On Feb 1, 2:20 am, Michael Easter <[email protected]> wrote: > > > My question: why not use video? > > If you can't get people to comment their code, I doubt you'll get them > to video it. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
