Well, this session was the one I was most excited to attend and maybe because of those high expectations was the most disappointed with. First, I’d just like to apologize to anyone that attended this session. I became “that guy” and I’m sorry for that. I disagreed with so much of what was being said by David, that I had a hard time keeping my mouth shut. Especially when I felt it wasn’t even a disagreement of opinion, but just wrong information being given. So for not allowing the presentation to just go on and instead interjecting constantly to disagree I apologize and hope I didn’t ruin that session too much for others.

Coding standards and best practices is a passion of mine and I have some very strong opinions about it. All in all, I’m glad the session was held because I think it’s important, but the delivery for me just wasn’t what I wanted. For me, I think it’s wrong to say “here is the standard you should use, and it should be an underscore to identify class level variable”, but more explain why you need to have standard for something, like why is it important to have some identifier for class level variables. I also felt that the book pimping was a bit out of control, but I guess that’s his right and just to make up for me being such an annoying ass to him, I’ll help him pimp it. Here check it out.

Even though I didn’t agree with all of his content, the general message is one I stand behind wholeheartedly, everyone who is a developer needs to follow some kind of standard. You need to do this at work and in your hobby projects. If you are writing code, you should have a standard and follow it.

So, one of my most disappointing sessions, I couldn’t keep my mouth shut, but overall the message still rings true. Props to David for presenting such a controversial topic, it’s always hard telling developers they need to change how they write their code, maybe next year I’ll have the guts to do one like this myself.