Programming patterns
What’s a good structure for your applications or in which way or in which structure should you program and should your program act? IT’s a questionthat every programmer faces and many have douts about the perfect structure. I’ve read about some structures and so but I didn’t begin using the pattern as it is called.
In software engineering, a design pattern is a general reusable solution to a commonly occurring problem in software design. A design pattern is not a finished design that can be transformed directly into code. It is a description or template for how to solve a problem that can be used in many different situations. Object-oriented design patterns typically show relationships and interactions between classes or objects, without specifying the final application classes or objects that are involved. Algorithms are not thought of as design patterns, since they solve computational problems rather than design problems.
Not all software patterns are design patterns. Design patterns deal specifically with problems at the level of software design. Other kinds of patterns, such as architectural patterns, describe problems and solutions that have alternative scopes.
Maybe the description gives a better idea of a pattern, we have to come up, not with ways to program and we must not care of how and where the files will be placed. Take rails, which is a nice framework but to do some things in code you will make it more complicated then needed.
Web based programs are programs made to execute tasks of normal .exe programs and for this group it is hard, I find, to use pattern.