Talk:Fishbowl

CS290F Fall 2006 - UCSB Computer Science - Thorsten von Eicken

Project Comments

This is a good project idea—I like it. The functionality is good too.

One major issue, however: you need to have some sort of transactional data that is not dream functionality. This is necessary for the fourth project to be meaningful, so it can't be only in the "maybe" functionality. Even if it's something very simple, there needs to be some transactionality here.

I also think the relationships between the data models may need to be tweaked a bit. I'm not entirely sure, but there's something here that doesn't quite gel for me.

• Users are obvious. These simply represent people who are logged into the system in any capacity.
• Employers represent companies, essentially (even if they may be single-person entities). Users may be assiciated with Employers as individuals who are authorized to create/update/delete job listings for Employers. This should be a many-to-many association since a single user, for example a headhunter, could be authorized for multiple Employers. Employers are created by Users and manged by certain users. I would say that each Employer needs a single owner (the creating User), and many authorized users.
• Applicants/Applications. I don't think having Applicants as a data model makes sense. An applicant is simply any User who has applied for a job. Therefore, all you really need is an association between Users and JobPostings. Any user who belongs to such an association is an applicant. You may, however want to make the join table a first-class entity called Application so that you can attach data to it (cover letter, customized resumé, etc.).
• JobPostsings: obviously you need these.

Good work, guys.

Stefan 15:05, 26 October 2006 (PDT)

• I only get the Rails "welcome aboard" page. Please fix & email me when done.
• Sounds like the EmployerTasks controller is ripe for splitting (at least according to the description on the web page): separate job listsings from applications, probably also separate out authorization piece.
• Your query SELECT joblistings.`id` AS t0_r0, joblistings.`employer_id` AS t0_ is going to give you trouble... You should consider using string prefix matches with indexes instead of the "like '%ca%'" stuff...
• Running some "explain" statement would probably bring up some more places where you need indexes...

TvE 00:11, 18 November 2006 (PST)

• Please implement a home page at '/'.
• The interface is difficult to guess. What am I searching for?
• You have a lot of duplicated data, it seems, is that on purpose?
• How do I see the details for a job posting? There's only an add-to-cart button?
• When I apply, it's pretty confusing that the entry just disappears from the cart. I'm not sure I understand the purpose of the cart, really. Also, I have no opportunity during the application process to review the documents that get attached, add some more, etc. Overall very bare bones...
• A little time spent to round out the flow through your site and a little better UI would make your site a lot more attractive. I don't mean fancy HTML, just having a few more pages with job details and thinking through the cart/application process so it's more natural.

TvE 08:23, 18 November 2006 (PST)

• Time to reorganize your information into multiple pages...
• How big is your database (rows/bytes)?
• I don't get much out of your graph. It just shows that as you increase load the queueing delay goes up. How many requests/sec are delivered? Look at a couple of other projects for inspiration on better presentation. Also, you do not explain your test setup enough.

TvE 00:04, 29 November 2006 (PST)