I prefer to write the backend first because thats how I think and it seems more logical to me, what do you prefer?
AceofSpades19 51 Junior Poster in Training
Dani 4,329 The Queen of DaniWeb Administrator Featured Poster Premium Member
Backend.
foke 0 Newbie Poster
I prefer to write the backend first because thats how I think and it seems more logical to me, what do you prefer?
Me too, as an standard.
Narue 5,707 Bad Cop Team Colleague
It depends on which makes more sense at the application level. I tend to work front end to back end in my designs. Writing and using the interface first helps one to understand and better design the implementation.
Freaky_Chris 299 Master Poster
I tend to rush some poor front end of some kind, so i can create the back end to interact with the front end more accurately. Then I go back and redesign the front end.
Sort of a testing/debugging front end more than an actually front end.
Chris
AceofSpades19 51 Junior Poster in Training
I tend to rush some poor front end of some kind, so i can create the back end to interact with the front end more accurately. Then I go back and redesign the front end.
Sort of a testing/debugging front end more than an actually front end.
Chris
thats actually not a bad idea
mustafaneguib 1 Junior Poster in Training
It depends on which makes more sense at the application level. I tend to work front end to back end in my designs. Writing and using the interface first helps one to understand and better design the implementation.
same here with me... i start with the front end so that i can get the design flow going, and also i prefer to use the top down design using the front side first.
Be a part of the DaniWeb community
We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.