java - Is it possible to have architecture guidelines? If so what should be in them? -


Similarly we have coding standards, what are the structures like architecture standards?

These will be high level principals, which we can pass to our less experienced programmers so that when they start designing changes or small applications, they know that the more experienced programmers are able to fix them. What we expect to see without doing (Note that this is not a review, rather than just preventing possible mistakes as soon as possible)

I think that potentially some things may be included in it such as "Always assume that your database is normal, unless a specific and clearly understood reason for not doing this", "always Separate out-of-presentation, logic and perseverance ".

Do people think that this would be very high level for any practical use? Or is it almost impossible to diversify the functionality of such generalization, which can be called code? Or can this be useful?

If you think that they are useful and realistic, what will you include?

(If it helps to clarify, then I have Java / .NET level programming for Corporate Style Business System).

will be a good place to start


Comments

Popular posts from this blog

c# - ListView onScroll event -

PHP - get image from byte array -

Linux Terminal Problem with Non-Canonical Terminal I/O app -