Beautiful name
Bears
Patterns of Enterprise Application Architecture "Enterprise Application Schema" Martin Fowler Power Press 2004 April Video Press
I have a pair of custom casual shoes, and I wrote "KISS" on a footwear. The other is written "YAGNI" - this is "black words" in the programmer circle, and I am a little showing it for my career. Let's mean "Keep IT Simple and Stupid" and "You Aren'tgonna Need IT". This is two rumors from agile communities. I am willing to stay on my shoes, let them remind themselves: don't over-pursue the perfection of programming, because I may never need that perfect design. However, I only did one of the last week: Reconstructing a project's business layer code, turning its architecture design from Transaction Script mode into Domain Model mode. If the software developer should always choose the simplest in all options, if the only purpose of programming is to achieve business needs, my behavior will not explain. Perhaps the only reasonable explanation can only be prejudice to the US. Plato believes that all things have a perfect, priori "理 e" (EIDOS), and what we have experienced is nothing more than this type of imperfect projection or replica - just like a mold Cake came out. If we are willing to inherit the worldview of the sages, then in my hand, the Patternal (Poeaa) in my hand is a "type of garden" that Plato is imagined. If you want to design advertisements for this Poeaa, I will say that it "carries Martin Fowler's Ideological Essence" --- "Idea" in English is just from the "EIDOS" of Greek This is also a coincidence in the word source. Martinfowler has a "godfather" in the object-oriented community - we certainly remember UML Distilled, Analysis Patterns and Refactoring. It is said that Mr. I have discussed OO technology in a technical seminar, when he learned that the other party was Thought Works employee, immediately said: "I actually tried to teach Martin Fowler's colleague OO technology. This is simply playing an ax in front of the carpenter, selling water on the side of the river. "As the most famous" missionary "in this circle, Martinfowler has a final summary, an outline. Many "Ancient Existing" technology have passed his mite gold, which is really popular among the developers - refactoring technology is the best example, and the recent example is Dependency Injection mode. From his work, we can clearly see that Martin Fowler has been committed to providing an enterprise-class application developer with a complete, self-sufficient discourse system, a typical world. Analysis Patterns tells us how to analyze user needs, refactoring tells us how to improve code quality, Planninge Xtreme Programming tells us how to plan agile development processes. This PoEAA is just the last piece of the puzzle, and the 47 modes of which it records cannot be avoided when the architecture enterprise application. Now, Martin Fowler's believers can use their own discourse to talk about enterprise-level applications. In the face of this Poeaa, a lot of readers will take this idea: Why do I want to use these modes? - This problem has been "why you want to reconstruct", "Why do you have multi-level structure," The subtext behind them is "Why I have to add these troubles to myself." Used too much from the praise of pragmatism: elegant design improve flexibility and reuse, so that the system is easy to maintain ... Hey, while doing design, think about "whether it needs flexibility here", I don't I think I have such a good energy.
