The PHP project and Code Review
Reading code is not only fun, its also a great way to exercise your brain - not to mention a fantastic way to discover new ways to solve problems. At work ( we are hiring btw !), for example, I read pretty much every single commit (and merge requests, for that matter) - and I'm subscribed to several different OSS commit lists. I can't say I read every commit to PHP, I focus on the areas I care about, but I do skim over the rest - if only just to see when new features are added. The PHP project has a good chunk of mailinglists , everything from support lists, developer discussions, QA, and so on. Every commit to our SVN is automatically posted to the relevant commit mailinglist(s). The main commit lists are; - PHP (php-cvs@lists.php.net, http://news.php.net/php.cvs ) - PHP Documentation (doc-cvs@lists.php.net, http://news.php.net/php.doc.cvs ) - PHP-GTK (phpgtk-cvs@lists.php.net, http://news.php.net/php.gtk.cvs ) - PEAR (pear-cvs@list...