Posted by fitzjarrell@cox.net on 08/15/07 13:56

On Aug 15, 7:57 am, Summercooln...@gmail.com wrote:
> On Aug 15, 5:21 am, "David Cressey" <cresse...@verizon.net> wrote:
>
> > <Summercooln...@gmail.com> wrote in message
>
> >news:1187176120.886269.130090@z24g2000prh.googlegroups.com...
>
> > > I wonder instead of just brainstorming, there probably is
> > > a very standard and a simple way to do database schema design.
>
> > > let's say we are doing a website. the user can go over
> > > and type in the movie name and zipcode, and the website
> > > will return all the theaters showing that movie and at what
> > > time, for theaters in THAT zipcode only (for simplicity).
>
> Nowadays when I go for interviews, many interviewers hope that
> I can produce a schema in just 2, 3 minutes...
>
> So I wonder for the example above, is there a 2 minute way of thinking
> to produce the solution?

The less time you spend in design the more time you'll spend later in
development costs as your 'model' will show its weaknesses (such as
being totally unscalable) and require MORE work than it would have
taken to build the application properly.

I suggest you stop being lazy and start being smart.


David Fitzjarrell

[Back to original message]