try-catch-FAIL

Failure is inevitable

NAVIGATION - SEARCH

What’s in your Definition of Done?

Every team, whether you are practicing agile or not, regardless of platform or language, should really have some Definition of Done.  What does it mean for a story/feature/defect/whatever to be “done?”  What things have to happen to achieve “done” status?  Defining these things will help with estimating effort, and it may also help increase the quality of your product.  Here are a few of the things I look for in a Definition of Done. More...

What questions should you ask if you are the interviewee?

Here’s another one for the non-.NET category.  I’ve been involved in both sides of the interview process recently.  I previously outlined the types of questions I ask if I’m in the interviewer seat, but what about about when I’m the interviewee?  Asking the right questions as an interviewee is just as important (if not more important) than asking the right questions as the interviewer.  The position you are interviewing for is going to play a major role in your life.  You need to find out now if it isn’t a good fit for you.  Here are some of the questions I like t... [More]

Data Access in Fail Tracker–Row-Level Security with LINQ to NHibernate

This is the third and probably final post about how data access is performed in Fail Tracker.  I’ve previously shown you the basics of how its repository-pattern based approach and how a shared base SpecsFor test fixture is leveraged to simplify testing.  In this post, I’ll show you how the decorator pattern is employed to provide simple, pain-free row-level security, ensuring that users can only see projects and issues that they’ve been granted access to. More...