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.
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.
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.
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.
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.
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.
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.
