I'm a supporter of Extreme Drinking Programming. It helped me through college so I think it'd be a great methodology for us to implement here. EDP incorporates several tried and true practices and expands upon them to improve your programming productivity. For instance, everyone knows the value of Buzzword Bingo. Well EDP puts the buzz in buzzword. Now whenever a buzzword is mention not only do you mark it down, you also take a shot. Lvl I developers do shots of beer, lvl II vodka, and lvl III shots of 151. Drunken documentation is another positive aspect of EDP. No one likes writing documentation, but when you have a couple of beers with it, it turns into a party. Also when managers or new employees have questions about unclear documentation you can honestly tell them to 'f:-) off, I was drunk'. Then there is the coding itself, the most integral part of the process. Rule number one is you have to chug while compiling. Because large projects provide an obstacle to this, programmers will keep their code short and simple so there will never be any problems with overcomplexity. Everytime you core dump you take a shot, and for bringing down a server with your code you have to do a kegstand. Always remember to intersperse coding with a few trips to Denny's and you will have a happy and healthy project that may smell a bit like puke, but will never let you down. - Frank