IMHO detailed code reviews would be excellent. They give credit where credit's due. They can inspire developers to take more care. And, possibly most importantly, they're highly valuable to people (relatively) new to Drupal development. Your review of linkdsb, for example, taught me a bunch of things on how it's done and how core should be an inspiration and starting point.
The rails community has therailsway.com, a code review blog that does just that. It's lead by two leading rails developers and is an excellent way to learn...
Cloverfield (2008; Holy crap, this was good. Would be a great double-header with The Host.); Communion (1989; Didn't work for me. Walken an odd choice, and it was more humorous than tense.); The 400 Blows (Criterion Spine #4) (1959; Truffaut's first feature; I'm looking forward to the Antoine Doinel followups.); Silent Rage (1982; Great beginning and Norris-appreciation, but slow and meandering ending.); Dakota Bound (2001; An actual plot, good cheesy action scenes, and lesbians. Amazingly good.);
D&D 4E: Treasure of Talon Pass (4E: we're just a combat engine! Buy miniatures.); D&D 4E: Monster Manual (A little too light on fluff for me. Prefer fluff.); Apple Volume 1 (As an art book, great. But for story? Bleh.); The Art of Dragon Magazine (I remember many of these from the original issues.); Mateki: The Magic Flute (I like Amano, but this felt like wasted sketches.);
IMHO detailed code reviews would be excellent. They give credit where credit's due. They can inspire developers to take more care. And, possibly most importantly, they're highly valuable to people (relatively) new to Drupal development. Your review of linkdsb, for example, taught me a bunch of things on how it's done and how core should be an inspiration and starting point.
The rails community has therailsway.com, a code review blog that does just that. It's lead by two leading rails developers and is an excellent way to learn...