'. '

InvitationForReaders

From APIDesign

(Difference between revisions)
Jump to: navigation, search
Line 1: Line 1:
Dear reader,
Dear reader,
-
maybe you are standing in the book store, holding this book in your hand and asking yourself: Shall I read it? Here is my answer: If you ''ever wrote a code'', handled it to another person and let that person compile own code against your one, then yes, you are eligible for entering the API design world. This book will help you explore it.
+
Maybe you are standing in a book store, holding this book in your hand while asking yourself: "Should I buy it?" Here is your answer: If you have ever written code, handed it to someone else to let them compile their own code against yours, then the answer is: "You are ready to enter the API design world and this book will help you explore it."
However, this book does not attempt to ''teach you API design in five easy lessons''. It cannot be read in ''three days''. If you are looking for such a fast handbook, then very likely this is not the book for you. On the other hand, if you are interested in deeper knowledge about API design, in knowing not only ''how'', but also ''why'', then do not return the book into the shelf, and let me introduce myself.
However, this book does not attempt to ''teach you API design in five easy lessons''. It cannot be read in ''three days''. If you are looking for such a fast handbook, then very likely this is not the book for you. On the other hand, if you are interested in deeper knowledge about API design, in knowing not only ''how'', but also ''why'', then do not return the book into the shelf, and let me introduce myself.

Revision as of 17:14, 4 May 2008

Dear reader,

Maybe you are standing in a book store, holding this book in your hand while asking yourself: "Should I buy it?" Here is your answer: If you have ever written code, handed it to someone else to let them compile their own code against yours, then the answer is: "You are ready to enter the API design world and this book will help you explore it."

However, this book does not attempt to teach you API design in five easy lessons. It cannot be read in three days. If you are looking for such a fast handbook, then very likely this is not the book for you. On the other hand, if you are interested in deeper knowledge about API design, in knowing not only how, but also why, then do not return the book into the shelf, and let me introduce myself.

My name is Jaroslav Tulach and I am founder and initial architect of NetBeans, which is not just the well known IDE, but also the first modular desktop application framework written in Java. My name sounds slavic and has strange pronunciation (read the initial J as Y and last ch as Spanish J) because I am Czech. However as NetBeans is a flagship software product of a Silicon valley company for a while, there is no need to worry the content of the book would not be widely applicable and understandable.

The book is based on notes, that I collected in the last ten years, designing and maintaining NetBeans APIs and transferring this knowledge to the rest of our developers. It is journal from the NetBeans laboratory that describes our problems, our growing understanding of them, the solutions we have chosen and the conclusions we made after applying them. Although our knowledge has been gathered while working on NetBeans, it is general and generalized enough to be useful for most software projects.

The knowledge of proper API design is essential for successful creation of 21st century software. Let this book be your guide when exploring the API design world.

Signed: Jaroslav Tulach

Personal tools
buy