On Friday I spoke at the 2010 Dallas Tech Fest. This is a great event and I look forward to it every year. This year, I spoke on the 10 Practices that every developer needs to start right now (slides). I also, found out later, that I had the most attended talk of the day – awesome! One of the things that I cover in that talk are the principals of SOLID – and that’s what I was heckled about.
This week I had the privilege of leading a custom workshop for a team of developers in Fort Worth, TX. One of the topics that we covered was Writing Testable Code; specifically, we looked at the Model-View-Presenter (MVP) patterns, dependency injection and using RhinoMocks to pull it all together. The one catch was… this group of developers used Visual Basic.
I’ve never shied away from VB. In fact, VB6 with classic ASP is where I cut my programming teeth, and VB.NET was my first move to a true OO language. That being said, I work day in and day out with C#… I’m much more fluent there, and I realized that there were a ton of new features in VB that I wanted to cover that I wasn’t up to par with, fortunately I was able to call on my network of super smart friends and recruit/hire a fellow MVP’er to help me out for the day (thanks Cory for doing that 2 days after your wedding!)
One of the things that tripped me up was using Lambdas in VB. Lambdas are especially important if you are going to use a Mocking framework like RhinoMocks (which I do). Doing Lambdas in VB – especially when I was trying to raise an event from a mock – sort of tripped me up…
First – if you are working with Rhino Mocks, you should go have a look at the excellent Wiki. http://ayende.com/Wiki/Rhino+Mocks+3.5.ashx I find that a lot of people (read: I had) skip the “documentation” since RhinoMocks is so fluent and straight forward, but it’s definitely worth the read!
Second, if you’ve never raised an event in mock from your test in C# here’s the code:
viewMock.Raise(x => x.CalcShippingRequest += null, this, EventArgs.Empty);
and in VB:
This post is the 6th in a series that started with the 10 practices that every developer needs to start right now
The first time that someone taught me about Software Design Patterns it went something like this:
I find that is how a lot of people react when they first learn about patterns. “So a pattern is just giving a name to good software development” Well, yes and no. On the one hand – yes, a software pattern is recognizing common software challenges and the approaches that have worked in the past to over come those challenges – and naming it. On the other hand, don’t underestimate the power of giving something a name.
This post is the 5th in a series that started with the 10 practices that every developer needs to start right now
When writing software, we often don’t think about the security implications of our actions. Probably because we write software to do something, we’re not always aware of what it shouldn’t do. Their are a lot of guidelines for writing secure code, and designing secure systems. Rather than going in to all of the areas, let me just hit on some of the especially important topics that I’ve come across…
This post is a part of a series that I started with “10 Practices that Every Developer Needs to Start Right Now“.
Update: This post was picked up by DZone, go vote it up!
Ok, before you dig in to the post, let’s get two things out of the way first. 1.Go read the authority on SOLID principles from the man himself, Uncle Bob Martin. 2nd.Go get the very cool Inspirational SOLID images from the guys over at Los Techies. They released them under a Creative Commons License which I think is pretty cool! Alright, got that out of the way? Good. Let’s get started.
Few things have come a long OO history that resonate so well with so many developers than the SOLID principle. One of the reasons they resonate with so many developers is because they communicate several practices that many developers have been doing all along. The beauty and power of the SOLID principals in in there ability to communicate, what I call code architecture, in such a memorable and practical way.
Like any good thing, however, taken to an extreme can become a hindrance on any project. So, I’m going to tackle these principals like I tackle everything in this series… give you my take on it. So here you go: SOLID according to Caleb.
I’m starting off this series talking about Object Oriented Programming. It’s amazing how many people write C# or VB (.NET) with long, procedural methods with really no understanding of the true fundamentals of OO design.
I know, I know – it’s not you, and know what? I’m not talking about you.. but check out the code from the person next to you. See what I mean?
Just because you’re writing in an OO language, doesn’t mean that you’re writing OO code, or taking advantage of the Object Oriented benefits. An Object Oriented language is more than classes with methods, properties and events (even VB 6 had that!).
Learn the Fundamentals.
If you are going to read through my “10 practices that every developer should start right now” series, then you probably want to know where these 10 practices came from, why I chose these 10 – really, what so important about secure coding anyway? 
– I think that it’s important to know that these aren’t just 10 random items to fill a couple of blog posts. These are all practices that have been thoroughly thought out. This list is something that I started to formulate over a year ago based on my experience as a consultant, working as a technical editor, and discussions with countless MVPs, other consultants and in my interviews with potential consultants… Read more »
Update: Since technically a DI Container could be considered part of SOLID, I’ve swapped it out for Secure Coding… more on this soon!
If I ever right a book on becoming a .NET Ninja, these are the things that I want to cover.
Eventually, I’d like to write a book and dedicate at least a chapter to each of these (although any one of these topics could be a book in and of itself) In the mean time, I think that I’ll start with a blog post on each one, and maybe make it a goal to eventually do a User Group talk covering each topic? I’m looking forward to flushing these out as posts. I hope that you will enjoy them too!
What sort of things would you add to the list?
Caleb Jenkins, is a recognized Silverlight expert, Software Mentor and Coach; he is the Founder and Principal Mentor for Proaction Mentors, he is also a National Speaker for INETA, a Technical Editor for Wrox Press and is a Microsoft MVP. You can follow him on Twitter or subscribe to his blog updates.
Caleb lives in the Dallas, TX area where he continues to date his beautiful wife and busy himself playing Candy Land and xBox 360 with their four incredible children. Eventually he’ll post some of the gazillion interviews that he's recorded on CommunityCast.tv or blog more... or stop speaking of himself in the third person. more...
If you're still reading this, then take a minute to subscribe to my RSS feed or sign up to receive updates by email
on Learning in Public – what I learned from being heckled at the Dallas Tech Fest
My Health Blog CommunityCast.tv
Twitter
Subscribe in a reader