Having read the comments, I havn't seen what I find to be the gravest problem with this article - the poor OO practices of the author.
Seriously. If you have a family of methods on a user that only work in the presence of an instance of a project, then the first thing you ask yourself should be 'hey, maybe these methods belong on the project instead' and not 'hey, lets reinvent nil'.
Comments
Having read the comments, I havn't seen what I find to be the gravest problem with this article - the poor OO practices of the author.
Seriously. If you have a family of methods on a user that only work in the presence of an instance of a project, then the first thing you ask yourself should be 'hey, maybe these methods belong on the project instead' and not 'hey, lets reinvent nil'.
Don't these methods only work in the presence of an instance of a user as well?