For Spring Interview Questions

visit

2008-08-26T02:21:00.000-05:00
For Spring Interview Questions

visit

http://techinterview.weebly.com/spring1.html

Thanks, Steve for pointing that out. I definitely ...

2007-02-23T07:44:00.000-06:00

Thanks, Steve for pointing that out. I definitely didn’t figure out that James code is about putting the methods on the Task object. This explains some of the things.

> project.active_task vs project.tasks.active

No, I didn’t intend to specify the project.tasks.active. There are a few reasons for that.
First, I didn’t event saw that James is doing that :-). I believed that project.active_task is more readable and it is showing the intent more clearly. Also, the statement project.tasks.active could be seen as kind of train-wreck and I generally don’t like this type of design. It could introduce difficulties with testing/mocking/refactoring/encapsulation and so on. Dave Astels had mentioned something similar in the comments of this blog: http://stevef.truemesh.com/archives/000500.html.

However, the difference here is that this method is added to the task association. I find that interesting and I will re-read James’ blog to see what else I have missed :-).

Thanks again for clarification.

Shouldn't your original spec have been like this: ...

2007-02-23T05:47:00.000-06:00

Shouldn't your original spec have been like this: http://pastie.caboo.se/42420

Jamis' code is adding the active and inactive methods to the tasks association, not adding the active_tasks method to the Project class.

Comments on Igor's Blog: Filtering has_many Associations in Rails

For Spring Interview Questionsvisit 2008-08-26T02:21:00.000-05:00 For Spring Interview Questionsvisithttp://techinterview.weebly.com/spring1.html

Thanks, Steve for pointing that out. I definitely ...

Shouldn't your original spec have been like this: ...

For Spring Interview Questions

visit

2008-08-26T02:21:00.000-05:00
For Spring Interview Questions

visit

http://techinterview.weebly.com/spring1.html