views:

165

answers:

4

I have been trying to write my first big web app (more than one cgi file) and as I kept moving forward with the rough prototype, paralelly trying to predict more tasks, this is the todo that got accumulated (In no particular order).

* Validations and input sanitizations
* Object versioning (to avoid edit conflicts. I dont want hard locks)
* Exception handling
* memcache
* xss and injection protections
    * javascript
    * html
* ACLs
* phonetics in search, match and find duplicates (for form validation)
* Ajaxify!!!

(I have snipped off the project specific items.)

I know that each todo will be quite tied up to its project and technologies used. What I am wondering though, is if there is a pattern in your todo items as well as the sequence in which you experienced guys have come across them.

+3  A: 

The Model-View-Controller (MVC) design pattern: decouples users inputs and the presentation layer from your application data.

Sylvain
+1  A: 

model view controller of course. start with some framework first. in php kohana is good , for python django is good, ruby on rail and so on...

iamgopal
+4  A: 

If this is actually a big web app that will be deployed for general consumption, then I'd add on Rate Limiting.

Jason Punyon
Yeah! that seems to be already either being discussed or in implementation in GAE. SO I think its the cherry on icecream.
+3  A: 

Almost all of your list is "Framework".

Almost none of that is functionality a user actually sees.

My to do list never looks like that. Never.

Consequently, I have this advice.

STOP.

Do this instead.

  1. Find a framework that does this.

  2. Focus on the the actual users and their actual use cases.

Now your todo list will have actual use cases that an actual user will actually care about. That's what should be on your todo list. Not framework technology. Use cases.

S.Lott
I have a different todo list for the use cases .. The list is not something I am going to write. The list is just a set of items I am going to "take care" one by one. What I am really interested in, is the sequence of things people take care (on the road from rough prototype to shiny professional app)But of course.. You did not know about my other todo list. My bad. Thanks a lot for pointing it out anyway. I bet a lot of newbies will find it helpfull.
@lankerisms: A to-do list that consists entirely of problems already solved by frameworks is not a list of things to **do**. It's a list of features. Just download a framework that has those features. Stop focusing on framework features.
S.Lott