I’ve been doing a lot of research on LINQ for episode 6 of the Coding Blocks podcast and I was a bit surprised by what I came up with.
I had originally thought of LINQ as a feature. I had heard the parable of the guy at the white board, writing what they thought code should look like and then worked backwards on how to get there. This makes sense, but what surprised me was just how much of the building blocks were already there.
Many years ago I purchased your book C# in Depth because I wanted to transition into C# development. I blogged about it, and you actually advised me to read something more introductory in the comments. 🙂
Many applications require customers (don’t call them users!) to sign up with a username or email address to use the service.
If a user mistypes their credentials, security best practices dictate that an error message be displayed which informs the customer that there was a problem WITHOUT revealing whether or not the username was found.
There are a lot of opinions around unit testing coverage tools, and I get the debate. However, if I’m working on a fun, no-deadline, side project then I don’t have a lot of excuses for ignoring it. Especially when dependencies are basically null, like ColorMine.