How do you know when it is time to use the framework for website development?

Question

I design websites in an n-tier structure and my requirements are still being met. But as powerful structures like Zend Framework , Symfony is becoming popular, I wonder how to find out if it's time to move on to the structure?

Am I in some kind of dilemma? What is the right option?

Answer 1

If you are satisfied in your own way - never. Frames are not written by the gods, but by people. Some of them may know less than you. Or have a different point of view.
In addition, it is more a paradigm dictated to you than a toolkit. Religion. If you have your own path, and it suits you, better develop your own structure. Not as versatile as the famous, but not as greasy and lethargic as they are.

Answer 2

Yes.

This not only speeds up development time (as soon as you know your way around the framework), it allows other developers to better understand how the site works.

Answer 3

Using a framework has, of course, its advantages, because you can write your code faster, you don’t worry about the many functions that are always required in a web application, so you can think more about your specific implementation of the application, and you just have to update other features. Using a structure gives you, of course, advantages in terms of cooperation, because, obviously, if you use a well-known structure, many people know about it without wasting time on training.

But, when you use the framework, you must respect its structure, its coding style and its design. This is usually not a problem, because if you choose a structure reasonably, you will not feel the need to leave the rails.

Answer 4

The best thing to do is just just go! I switched from my own coding style to CakePHP about a year ago and did not look back. It is much easier for me to work with other code based on the framework of other people, and in general this led to the reduction of wtfs to my own code after six months, because now the code follows much more strict formats and is more predictable.

If you ask this question, then the time to try it is probably now, since you are clearly interested in your interest. If it turns out that you don’t like working with them, you can always go back to your usual path (or even write your own, as Colonel Shrapnel says).

Answer 5

4 reasons why we decided to go with a card (Zend) in my company:

1 - General syntax: the framework has its own syntax that all our encoders should work (to some extent). Easier to use external developers or handle staff turnover

2 - Scale: the site in question had a scale requiring MVC architecture

3 - Tested components. The structure has most of the finished components, which allows you to focus on the model

4 - Brand trust: there is a certain value when using a brand with a high profile from the point of view of the client. This implies a standard solution and "separates" the client from your custom infrastructure.

Answer 6

Whenever you are not quite sure what the end result of the software will be. Ready-made libraries are usually processed almost so that you can easily expand your site. And if at some point in the future new people work, they can easily jump without learning their way to do something.

But other than that, I think Colonel Shrapnel is in place.

Answer 7

Until you can answer this question yourself, I would say: Always use the framework.

I know many developers who think that using the framework makes them less "real programmers" who are just plain stupid. This wrong pride should not interfere with the creation of well-structured and maintained code.

Using a good Framework saves you from many unpleasant problems, so you can focus on your real project. Of course, there are no things that you cannot get around without a frame, but with one you can make them much faster and with a headache.

Perhaps experience will show you cases when you do not need a framework or are actually better than one, but they are quite rare.