All geek questions in one place

Is MVC incompatible with Agile?

Agile emphasizes fast iterations without wasteful planning.

MVC emphasizes separation of concerns based on planned architecture.

Since non-MVC technologies require less planning, can they be more suitable in an Agile project?

+3
source share
5 answers

Separating problems does not require you to plan every detail before you start coding. And moving does not mean that you just write down the code as soon as it comes to mind. Agile means that you are not too attached to your initial idea of ​​how the project will look and be ready for a refactor if necessary (as is usually the case), without fear of throwing large pieces of code into the process.

Separating issues can very well make refactoring much easier, so MVC can be a great helper for flexibility.

+30
source

Agile development is usually a process of rapid prototyping and refactoring. Separating MVC issues can often simplify and speed up both processes.

+3
source

. , . , . , , , . , , , , , .

, MVC . , , , API. . , , , API. API , API, ( , , ).

+2

, .

() MVC-, , , .

, - "", 1 . , 1 , 1-2 .

.

+1

agile - " , ".

:

  • script
  • -
  • , wiki
  • single-user single-page editor "just edit the data"

Then they will not have MVC and will be suitable flexible solutions.

If from the very beginning of the project it is obvious that none of this will come close to solving the problem, it would be pointless to literally try them and wait for the failure before trying to implement the next simplest solution.

+1
source

Source: https://habr.com/ru/post/1717577/

More articles:


All Articles