Design Pattern-start a new journey based on engineering implementation

Two years later, another round of technological development has taken place. I have a very different mood when I look at the books I wrote two or three years ago.

In the past two years, the project scope is getting wider and wider, and the scale is getting bigger and bigger. Every time a project goes online, I always think, "If it was .... "It will not be so messy. The projects that have been taught to me over the past 10 years have taken place.

 

C # has changed a lot in the past two years. The language is more concise and clear. generics, attribute, and anonymous delegation are still my favorites, and now I have added them to the list.

I can see that they have become the leading character in entlib and unity, so the project gap has always wanted to make a big adjustment to the original book, and write it again with a more in C.

 

Not only that, but the biased understanding of Java two years ago made me look at the Java EE system with colored eyes. After more than two years of hybrid development, I found that C # and Java have their own scenery, C # is a mountain, and Java is a sea.

Currently, Java is not the one I used more than 10 years ago. annotation, generics, and enum have their own characteristics. Scea 5 also made me more interested in the Java EE system.

 

There are several considerations before you try again:

1. The original book is too thick. Gof 23 should be independent as a book, while scea and application architecture guide should be combined in the future to form an independent book. If possible, the security mode should be combined with the security development lifecycle (SDL.

2. Parallel companion articles on C #4.0 and Java SE 6

3. It is widely felt that the original book language is too blunt, so I will certainly listen to your opinions and make the text more concise and simple.

4. target readers I want to make adjustments. The classic content of each mode needs to be compressed.

5. The basic part of Object-Oriented Design for C # and Java should be added and deleted in conjunction with the new version of language.

6. In addition to interface-oriented programming, we should introduce Di and fluent interfaces in an all-round way.CodeDownstream users are more comfortable and casual

 

In addition, I have known many friends through this book over the past few years, and my practical engineering experience has given me a lot of guidance and inspiration, I hope to get comments, suggestions, and criticism from you again on the way to the new expedition.

 

Today is a rare good weather in Beijing, staring at the "Blue Sky" and taking a new look.