Wireless Adapter Traps Linksys E4200: Retrospective A simple way to see if someone is spam scamming you How to resolve a complex type as a string implicitly How to use a complex type in a conditional
Wireless Adapter Traps Ok so you go to the store and you’re looking around for an awesome deal on a Wireless-N adapter, and you find one for only $14!  ”How can this be!?” you might ask yourself?  Well, let me explain something to you before you end up with the same situation I find myself in right now.
Linksys E4200: Retrospective I just recently retired my WRT54G in favor or a Wireless N Router.  I ended up going with the Linksys E4200 for a number of reasons.
A simple way to see if someone is spam scamming you I hate having to sign up for anything on the internet. If I can avoid it I will, but nevertheless at some point you’re going to have to sign up for something.
How to resolve a complex type as a string implicitly Along the same lines as resolving a complex type in a conditional, I also want to be able to take the same Authorization Result, and use it to broadcast a message to the system (or user), and tell them why couldn’t they be authorized.
How to use a complex type in a conditional I am building a basic authorization framework, and I have really liked the use of it so far. It basically looks something like this
Datastructures, Objects, and why Hybrids are evil

I was writing this code that let’s interviewees code problems for me, and it verifies that the interviewee actually writes something that works. I got to a point in my printer classes that I wasn’t liking, and I thought I’d share it.

 
Recruiters, if you’re doing this you’ve already lost

I received an email this morning regarding an “urgent” position that needed to be filled. I get these all the time, but what really struck a cord with me was the last part of the email where the recruiter actually wanted me to fill out all my information in an HTML form that he put into the email.

 
Team Maturity

This isn’t an original idea of mine. It actually comes straight from 5whys.com. I spend a lot of time as a leader researching how others lead their teams, and @RoyOsherove‘s writings are worth your time.

 
SOLID Principles: Liskov Substitution Principle

Liskov Substitution Principle, or LSP, is actually a very simple concept to understand in a strongly typed language. In languages like C#, or VB.NET, LSP often gets taken for granted, but I’ve seen cases where even in strongly typed languages you can violate LSP.

 
SOLID Principles: Open Closed Principle

This has been done to death I think, but I wanted to take a shot at it. In fact, this is really more for my benefit than for anyone else. If I can manage to explain these concepts clearly enough then I think I have a firm understanding of what they actually stand for, and how I should apply them when I build things. The first thing we’re going to get into is the Open Closed Principle.

 
Interviewing: Done Easy

When I develop applications, any time I can forgo repeating myself I usually take the opportunity to save myself the time. The same applies to a lot of my daily routine at work. If there’s a way I can do things better, I’m all about it. So when I started conducting interviews, the first thing I started thinking about was how I can make this as stream lined as possible.

 
ASP.NET MVC Model Binding: The Ins and Outs

Model Binding can be a tricky thing to get right with MVC. Dealing with flat POCOs works fine, but when you start getting into more complex, truly object oriented domain objects, things get out of hand pretty quickly.