360Flex Speakers make their own standards

360|Flex speakers love to start crazy projects like degrafa and openflux. They start their own application frameworks like Mate and Swiz. However, none have ever tried to incite riots. Well, okay, so maybe a few have (i.e. Doug McCune, Sim Batemen, Ryan Friggin' Stewart), but none have so boldly stated it as Sam Rivello.

In an email to John and I, he actually says:

I'm hoping to get mad feedback and insight riots.

I come from Los Angeles, so I love a riot just as much as the next guy. (I ain't a looter though, DESPITE what that video camera shows!) Therefore, I refer you all to Sam's blog to read up on his Coding Standards doc. His post is a month old, but I still think very relevant. I'm just slow in writing blog posts. (Ask John about just how slow I am). Go read it and getcha riot on! :)

The Flex team has released their Coding Standards as well. Tariq Ahmed did one too awhile back, but I can't seem to find the link. (Someone post it in the comments if you know it.)

I personally wouldn't have the patience to write my own conventions, but I love to use them. Gimme an example to follow, and I'll follow. It's sad how many people let their preference get in the way of clean, coherent code. I worked a Y2K project at Bank of America once. I asked the Project Manager for their Coding Conventions doc. As he handed me the 300 page printout doc (It was all languages and styles; I just used/read a sliver of it), he said, "You know, in all the time I've been here, you're the only one who has ever asked for this." Sad.

So if you and your team aren't cohesive yet, go get cohesive. When you see Sam in San Jose, be sure to thank him for taking the time to help out lazy coders like me. :) Buy your ticket soon though, I'm sure many will come to see the hopeful riot Sam wants to start!