“There are more than enough design books in the programming world already,” you might
think. In fact, there are so many that it makes sense to ask why I would write—and especially
why you would read—yet another one. Particularly, there is the famous Design Patterns: Elements
of Reusable Object-Oriented Software,1 about design patterns in object-oriented
systems, written by the so-called “Gang of Four,” which is a must read for every developer
making use of any object-oriented language. In addition, there are many specialized books
describing design patterns, all of them useful when writing specific types of applications.
Moreover, there is the unofficial Java programmer’s bible, Effective Java.2 In light of these facts,
is there really a need for yet another design book?
I believe the need exists. I’ve been designing NetBeans APIs—that is, application programming
interfaces—since 1997. I’ve passed through almost all the possible stages a person
designing a framework or a shared library can pass. In the early days, I slowly gained a feel for
the Java language while trying to apply coding styles that I knew worked well in other languages.
Later, I became fluent in Java. At that point, applying various known patterns to my
code written in Java seemed so simple, although after a while I realized that things are not
always as easy as they seem. I realized that traditional patterns are not appropriate for an
object-oriented application framework such as NetBeans, and that you need a completely
different set of skills.
📚作品详情
文件名称：《Practical.API.Design.Confessions.of.a.Java.Framework.Architect》
更新时间：2020-05-02
详情列表:
💡声明
本站收录优秀作品内容、精彩书评、互联网技术文章、软件使用手册、书籍作品杂谈等内容，不提供电子书下载，请自行搜索下载或购买正版。如有读书交流沟通的想法可联系taoshuzhai521@163.com。博主会第一时间反馈，谢谢合作！