How are new programming frameworks helping analysts, designers and programmers work better together?

It could be a water drop, iterative or agile development, or something else. Regardless of which mode of the development life cycle we are talking about, there are always several points of view for the same problem. From business to problematic, as well as programming, testing, etc.

So the question is, how do modern companies use modern best practices to translate source code requirements?

How does the new programming framework help analysts, designers and programmers work together?

New means those that are most actively used at present. Python or PHP do not leave new ones, but they are actively developing a lot of fun and specialists. Core Workflow, AJAX, F #, etc. - brand new and gives developers additional productivity. But how do they affect team productivity?

0


source to share


3 answers


The framework only provides 2 things:

  • A vocabulary that is the same for everyone, so you can communicate and know that you are talking about the same thing.
  • A process for people to follow if you get confused.


The rest is up to you as a team.

+1


source


To be clear, some of your examples are not really programming / programming frameworks . Python, PHP and F # are complete programming languages. AJAX sits in the gray area between the framework and the library . Perhaps your Workflow Foundation is your best example.

A good structure gives the team these advantages:

  • A consistent way to accomplish common tasks. This makes it easier for the developer to read and edit other developer code, which makes everything more productive.
  • Automation of common tasks. If you turn off busy work, team members can focus on solving problems. You can also shorten your team. Communication is easier in a small team.
  • Separation of group concerns. For example, in an MVC framework, a designer might work on a view while a developer is working on a controller and another developer is working on a model (in theory).
  • Rapid Development / Prototyping - Good structure shortens the feedback loop between analysts and developers, making the inevitable changes easier and faster.


Frames also have disadvantages:

  • Automation and pattern are out of the box. This may make the solution good, but not the best.
  • Once the team is ingrained, they cannot recognize when it is time to abandon structure for a complex task. Instead, they code a complex and hard-to-maintain framework solution. "When you have a hammer ..."
  • Frames can be overkill for simple tasks. Using them could make the solution more difficult, not less.
+1


source


Am I the only person who thinks you typed one of your homework assignments and now want us to do the homework for you?

No sane person actually phrases questions this way, it smells like a professor of linguistics.

0


source







All Articles