LA Code Camp, 11/2014

If you're a developer, and you have never been to a "Code Camp" before, you are missing out... Especially if you're a .NET developer, as there is a heavy .NET presence.  These are absolutely awesome two day conferences that are free (as in beer) for anyone to attend, and all of the speakers are volunteering their time and efforts to help others in the developer community.  As a resident of San Diego, I attend all 3 SoCal Code Camps each year, and I suggest you check them out.  Code Camps exist all over the country (maybe in other countries too??), so if you're not from SoCal, never fear... Google about to find your closest Code Camp!

This past weekend was the most recent Code Camp, this one was up in LA on the USC Campus.  It was a fantastic weekend where I got to reconnect with friends and colleagues old and new, and I got to see some sessions that were nothing short of inspiring.  My only regret... And this is the same regret I have after every code camp... Is all of the great sessions I missed in order to attend some other session (or while giving my own)!  I'm already looking forward to the next Code Camp.  Tons of thanks to all the hard work the organizers put in!

I want to thank everyone who came out to my "Debugging Tips and Tricks" session. I was honored and humbled by the number of people who came to hear the talk, and I hope everyone got a tidbit or two they had not yet known about, because my tap dance routine in the middle was pretty horrible... And short (you're welcome).

If you're interested in reviewing the slides and grabbing the links from within, the link to them is posted up on my SpeakerRate page for this talk.  You can just click the "slides" link to get to the presentation, but if you have a minute to rate the talk and provide any feedback, I'd love to hear what you have to say so that I can improve the talk for next time.  Thank you again for coming!

I'll leave you with one last awesome error message from a bug I stumbled upon back in 2012, while tinkering around with iOS development.  This is the error message... Which I'm pretty sure was not supposed to make it into production... That I received just as my Xcode IDE went crashtastic on me: