Answer the question
In order to leave comments, you need to log in
Development from the end
Greetings, dear Habrasobshchestvo!
Right now I’m working on one project (web) - I decided to try to move away from the traditional development process and try to lead it “from the end” - that is, first I write controllers, models, views, and then the actual implementation of their execution. Well, for example, first I write a controller (examples in php, because development is underway on it, dear)
class Controller_Posts extends Controller {
public function action_list()
{
$posts = Model::select('post');
$this->request->body = View::factory('list', array('posts' => $posts));
}
}
Answer the question
In order to leave comments, you need to log in
The question is really interesting, although I do not do it. But I searched the Internet and this is what I found
goo.gl/HgEOo
Bottom-up programming ("programming from the bottom up") is a software development technique in which large blocks are assembled from previously created small blocks. Bottom-up programming begins with the development of key procedures and routines, which are then constantly modified.
Top-down programming (“top-down programming”) is a program development technique in which development begins with the definition of goals for solving a problem, followed by sequential detailing, ending with a detailed program.
If I understood your question correctly, then you have the 2nd type.
If you didn't, then I'm sorry. It was interesting to search. If my answer is not correct, I will look forward to the correct one.
Well, it's not quite the reverse order of development. It's still planning - implementation - testing. With the proper level of planning, the implementation of this whole thing can go from complex to simple, although they usually go from simple to complex in order to see all the nuances.
I didn’t find any mention of your case on the Internet, but most describe the implementation stage as a set of necessary actions. I think it is more correct to argue that at the design stage, which is always before implementation, we must also develop the structure of the software. If further development (implementation) is carried out from top to bottom, and not from bottom to top (from simple to complex), there will simply be more problems in implementing individual functions (implementing their execution).
Sorry if I couldn't help. The question is certainly interesting, but in all areas of activity it is usually recommended to go from simple to complex.
If you first write tests to the controller that create fake and / or mock models and views, then there will be TDD :)
I have been using an IPS monitor for 5-6 years. And all this time he pleases me with the quality of the picture, and the response time, and viewing angles. So as soon as I decide to change to something bigger, I will definitely take the same IPS. For example, something like this: market.yandex.ru/model.xml?modelid=6195361&hid=91052
At the beginning of the month I bought myself a second ViewSonic vp2365wb.
PS Perhaps you should postpone the purchase a little? I don’t know how it is in your area, but our prices have skyrocketed. I managed to order for 9700r, now it costs about 11000r.
PPS... the toad crushes me even for other people's money... =)
I've had a DELL 2007WPF with IPS for a couple of years now.
Dell 2209WA do not take. it has a resolution of 1680x1050. but the Dell UltraSharp U2311H would be a great buy.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question