bryanthompson's Journal: asdf

asdf

Usually...

[Iamthefallen]

DB table schema goes first to get the basic storage setup.

Then the middle tier and a rudimentary UI to get to a working prototype.

While I develop the UI I ususally also build the views and CRUD stored procedures as I can better see what has to be presented when I have something to look at.

With the views and procs in place I can finalize the UI.

dot dot dot

[FroMan]

Usually I will design my APIs first. This allows me to see the data flow within the application. It gives me a rough framework to look at the application also, so I know where my critical points in development will be. This also gives an oppertunity to develop test cases early on also.

Second I'll work on the database design since I now have a pretty good idea of what kind of data the application is going to be working with. However, this can evolve quite a bit over time since I am looking at additional

Re:

[account_deleted]

Comment removed based on user account deletion

Re:

[account_deleted]

Comment removed based on user account deletion

Re:Without having much programming experience

[blinder]

hmmm, well pseudo coding if that's what you are talking about does indeed help flesh-out the requirements. i'll either start with some pseudo coding, to even some functional code to get an idea for the problem, but ultamtely starting with the data model not only gives you a good understanding of the problem, but also how your objects will look, how your program will have to operate, things like that.

that's why i almost always start with the database. i'll design the core set of tables first, and because i u