more often than not when i develop something i start with the front-end and then add the back-end while i design. this hasn't always worked out well. some applications will end up half complete, poorly implemented, or they develop featureitis because i don't stick to a specification for the design.
but with my current project i decided to start with the model. im creating the database, populating it with test data then am going to move on to coding the model with the controllers and views coming at the end. i dont plan to add a front-end until the data is being displayed plain as white bread. so far this is working out really well. i find it easier to stay focused and make progress.
how do you usually go about designing your application what works for you?
whats your design process?
Moderator: General Moderators
- daedalus__
- DevNet Resident
- Posts: 1925
- Joined: Thu Feb 09, 2006 4:52 pm
Re: whats your design process?
The front-end and back-end should share as much of the same code as possible. My design process is test first.
http://www.extremeprogramming.org/rules/testfirst.html
If you are ready to take your programming to the next level, you should read this book http://www.amazon.com/Test-Driven-Devel ... 0321146530
It only takes about 3 days to work thru all the examples. Actually type in the examples as you go and you will be a pro in no time. You will become test infected http://junit.sourceforge.net/doc/testin ... esting.htm
You won't look at programming the same ever again, and you wont look back. Those who I have explained the concept to either 1) didnt get it and rejected it, 2) made sense of it and adopted it right away, or 3) were already doing it (and better than me)
All professional developers do testing, from Nasa to Boeing, from PHP to Google Chrome, from Yahoo to Google.... If you don't have tests I don't take you seriously
some people definite "legacy code" as any code without tests. When you look at it that way it doesnt make much sense to write code today that is tomorrow's legacy code
http://www.extremeprogramming.org/rules/testfirst.html
If you are ready to take your programming to the next level, you should read this book http://www.amazon.com/Test-Driven-Devel ... 0321146530
It only takes about 3 days to work thru all the examples. Actually type in the examples as you go and you will be a pro in no time. You will become test infected http://junit.sourceforge.net/doc/testin ... esting.htm
You won't look at programming the same ever again, and you wont look back. Those who I have explained the concept to either 1) didnt get it and rejected it, 2) made sense of it and adopted it right away, or 3) were already doing it (and better than me)
All professional developers do testing, from Nasa to Boeing, from PHP to Google Chrome, from Yahoo to Google.... If you don't have tests I don't take you seriously
some people definite "legacy code" as any code without tests. When you look at it that way it doesnt make much sense to write code today that is tomorrow's legacy code
- daedalus__
- DevNet Resident
- Posts: 1925
- Joined: Thu Feb 09, 2006 4:52 pm
Re: whats your design process?
yeah ive been reading about it lately. i remember when people first started adopting it here i thought it was unnecessary for a lot of web development but the scope and complexity of my current project has me adopting new methods. thanks for the book recommendation