InvitationForReaders - Revision history

JaroslavTulach at 05:53, 25 May 2019

JaroslavTulach — Sat, 25 May 2019 05:53:09 GMT

←Older revision		Revision as of 05:53, 25 May 2019
Line 1:		Line 1:
	Dear Reader,		Dear Reader,
-
	you can buy the [http://practical.apidesign.org Practical API Design] book [http://practical.apidesign.org here]. Or find it at [[SafariOnline]].		you can buy the [http://practical.apidesign.org Practical API Design] book [http://practical.apidesign.org here]. Or find it at [[SafariOnline]].

JaroslavTulach at 05:52, 25 May 2019

JaroslavTulach — Sat, 25 May 2019 05:52:50 GMT

←Older revision		Revision as of 05:52, 25 May 2019
Line 1:		Line 1:
	Dear Reader,		Dear Reader,

-	you can buy the [http://practical.apidesign.org Practical API Design] book [http://practical.apidesign.org here]. Or:	+	you can buy the [http://practical.apidesign.org Practical API Design] book [http://practical.apidesign.org here]. Or find it at [[SafariOnline]].

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

JaroslavTulach at 05:24, 29 July 2018

JaroslavTulach — Sun, 29 Jul 2018 05:24:52 GMT

←Older revision		Revision as of 05:24, 29 July 2018
Line 1:		Line 1:
	Dear Reader,		Dear Reader,

-	Maybe you are standing in a book store, holding this book in your hand, and asking yourself: "Should I buy it?" Here is your answer: If you have ever written code and handed it to someone else to let them compile their code against yours, the answer is: "You are ready to enter the [[API]] design world and this book will help you explore it."	+	you can buy the [http://practical.apidesign.org Practical API Design] book [http://practical.apidesign.org here]. Or:
		+
		+	Maybe you are standing in a book store, holding this book in your hand, and asking yourself: "Should I buy it?" Here is your answer: If you have ever written code and handed it to someone else to let them compile their code against yours, 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 [[API]] design in five easy lessons". It cannot be read in "only three days!". If you are looking for a quick handbook, probably this book is not for you. On the other hand, if you are interested in a deeper knowledge of [[API]] design, in knowing not only the ''how'', but also the ''why'', let me introduce myself to you before you put this book back on the shelf.		However, this book does not attempt to "teach [[API]] design in five easy lessons". It cannot be read in "only three days!". If you are looking for a quick handbook, probably this book is not for you. On the other hand, if you are interested in a deeper knowledge of [[API]] design, in knowing not only the ''how'', but also the ''why'', let me introduce myself to you before you put this book back on the shelf.

JaroslavTulach at 07:04, 21 October 2009

JaroslavTulach — Wed, 21 Oct 2009 07:04:13 GMT

←Older revision		Revision as of 07:04, 21 October 2009
Line 5:		Line 5:
	However, this book does not attempt to "teach [[API]] design in five easy lessons". It cannot be read in "only three days!". If you are looking for a quick handbook, probably this book is not for you. On the other hand, if you are interested in a deeper knowledge of [[API]] design, in knowing not only the ''how'', but also the ''why'', let me introduce myself to you before you put this book back on the shelf.		However, this book does not attempt to "teach [[API]] design in five easy lessons". It cannot be read in "only three days!". If you are looking for a quick handbook, probably this book is not for you. On the other hand, if you are interested in a deeper knowledge of [[API]] design, in knowing not only the ''how'', but also the ''why'', let me introduce myself to you before you put this book back on the shelf.

-	My name is Jaroslav Tulach and I am the founder and initial architect of [[NetBeans]], which is not just a well known IDE, but also the first modular desktop ''application framework written in [[Java]]''. My name sounds Slavic and has a strange pronunciation (read the initial [[wikipedia::Palatal_approximant\|J as Y]] and [[wikipedia::Ch_(digraph)#Ch_in_Czech\|last ch as in Scottish ''loch'' or in German ''Bach'']]), because I am Czech. However, as [[NetBeans]] has been the flagship software product of [[Sun]] Microsystems for a while now, you don't have to worry that the content of the book might not be ''widely applicable'' and understandable.	+	My name is [[User:JaroslavTulach\|Jaroslav Tulach]] and I am the founder and initial architect of [[NetBeans]], which is not just a well known IDE, but also the first modular desktop ''application framework written in [[Java]]''. This book is based on notes that I have collected over the last ten years, while designing and maintaining [[NetBeans]] [[API]]s and transferring this knowledge to the rest of our developers. It is a journal from the heart of the [[NetBeans]] laboratory, describing 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'' enough to be ''useful'' for most software projects.
-		+
-	This book is based on notes that I have collected over the last ten years, while designing and maintaining [[NetBeans]] [[API]]s and transferring this knowledge to the rest of our developers. It is a journal from the heart of the [[NetBeans]] laboratory, describing 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'' enough to be ''useful'' for most software projects.	+

	Knowledge of proper API design is essential for the successful creation of 21st century software. Let [[TheAPIBook\|this book]] be your guide while exploring the big wide world of [[API]] design.		Knowledge of proper API design is essential for the successful creation of 21st century software. Let [[TheAPIBook\|this book]] be your guide while exploring the big wide world of [[API]] design.

	[[User:JaroslavTulach\|Jaroslav Tulach]]		[[User:JaroslavTulach\|Jaroslav Tulach]]

JaroslavTulach at 07:02, 21 October 2009

JaroslavTulach — Wed, 21 Oct 2009 07:02:56 GMT

←Older revision		Revision as of 07:02, 21 October 2009
Line 5:		Line 5:
	However, this book does not attempt to "teach [[API]] design in five easy lessons". It cannot be read in "only three days!". If you are looking for a quick handbook, probably this book is not for you. On the other hand, if you are interested in a deeper knowledge of [[API]] design, in knowing not only the ''how'', but also the ''why'', let me introduce myself to you before you put this book back on the shelf.		However, this book does not attempt to "teach [[API]] design in five easy lessons". It cannot be read in "only three days!". If you are looking for a quick handbook, probably this book is not for you. On the other hand, if you are interested in a deeper knowledge of [[API]] design, in knowing not only the ''how'', but also the ''why'', let me introduce myself to you before you put this book back on the shelf.

-	My name is Jaroslav Tulach and I am the founder and initial architect of [[NetBeans]], which is not just a well known IDE, but also the first modular desktop ''application framework written in [[Java]]''. My name sounds Slavic and has a strange pronunciation (read the initial [[wikipedia::~~http://en.wikipedia.org/wiki/~~Palatal_approximant\|J as Y]] and [[wikipedia::~~http://en.wikipedia.org/wiki/~~Ch_(digraph)#Ch_in_Czech\|last ch as in Scottish ''loch'' or in German ''Bach'']]), because I am Czech. However, as [[NetBeans]] has been the flagship software product of [[Sun]] Microsystems for a while now, you don't have to worry that the content of the book might not be ''widely applicable'' and understandable.	+	My name is Jaroslav Tulach and I am the founder and initial architect of [[NetBeans]], which is not just a well known IDE, but also the first modular desktop ''application framework written in [[Java]]''. My name sounds Slavic and has a strange pronunciation (read the initial [[wikipedia::Palatal_approximant\|J as Y]] and [[wikipedia::Ch_(digraph)#Ch_in_Czech\|last ch as in Scottish ''loch'' or in German ''Bach'']]), because I am Czech. However, as [[NetBeans]] has been the flagship software product of [[Sun]] Microsystems for a while now, you don't have to worry that the content of the book might not be ''widely applicable'' and understandable.

	This book is based on notes that I have collected over the last ten years, while designing and maintaining [[NetBeans]] [[API]]s and transferring this knowledge to the rest of our developers. It is a journal from the heart of the [[NetBeans]] laboratory, describing 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'' enough to be ''useful'' for most software projects.		This book is based on notes that I have collected over the last ten years, while designing and maintaining [[NetBeans]] [[API]]s and transferring this knowledge to the rest of our developers. It is a journal from the heart of the [[NetBeans]] laboratory, describing 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'' enough to be ''useful'' for most software projects.

JaroslavTulach at 07:01, 21 October 2009

JaroslavTulach — Wed, 21 Oct 2009 07:01:52 GMT

←Older revision		Revision as of 07:01, 21 October 2009
Line 5:		Line 5:
	However, this book does not attempt to "teach [[API]] design in five easy lessons". It cannot be read in "only three days!". If you are looking for a quick handbook, probably this book is not for you. On the other hand, if you are interested in a deeper knowledge of [[API]] design, in knowing not only the ''how'', but also the ''why'', let me introduce myself to you before you put this book back on the shelf.		However, this book does not attempt to "teach [[API]] design in five easy lessons". It cannot be read in "only three days!". If you are looking for a quick handbook, probably this book is not for you. On the other hand, if you are interested in a deeper knowledge of [[API]] design, in knowing not only the ''how'', but also the ''why'', let me introduce myself to you before you put this book back on the shelf.

-	My name is Jaroslav Tulach and I am the founder and initial architect of [[NetBeans]], which is not just a well known IDE, but also the first modular desktop ''application framework written in [[Java]]''. My name sounds Slavic and has a strange pronunciation (read the initial J as Y and last ch as ~~Spanish J~~), because I am Czech. However, as [[NetBeans]] has been the flagship software product of [[Sun]] Microsystems for a while now, you don't have to worry that the content of the book might not be ''widely applicable'' and understandable.	+	My name is Jaroslav Tulach and I am the founder and initial architect of [[NetBeans]], which is not just a well known IDE, but also the first modular desktop ''application framework written in [[Java]]''. My name sounds Slavic and has a strange pronunciation (read the initial [[wikipedia::http://en.wikipedia.org/wiki/Palatal_approximant\|J as Y]] and [[wikipedia::http://en.wikipedia.org/wiki/Ch_(digraph)#Ch_in_Czech\|last ch as in Scottish ''loch'' or in German ''Bach'']]), because I am Czech. However, as [[NetBeans]] has been the flagship software product of [[Sun]] Microsystems for a while now, you don't have to worry that the content of the book might not be ''widely applicable'' and understandable.

	This book is based on notes that I have collected over the last ten years, while designing and maintaining [[NetBeans]] [[API]]s and transferring this knowledge to the rest of our developers. It is a journal from the heart of the [[NetBeans]] laboratory, describing 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'' enough to be ''useful'' for most software projects.		This book is based on notes that I have collected over the last ten years, while designing and maintaining [[NetBeans]] [[API]]s and transferring this knowledge to the rest of our developers. It is a journal from the heart of the [[NetBeans]] laboratory, describing 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'' enough to be ''useful'' for most software projects.

JaroslavTulach at 15:24, 12 August 2009

JaroslavTulach — Wed, 12 Aug 2009 15:24:24 GMT

←Older revision		Revision as of 15:24, 12 August 2009
Line 7:		Line 7:
	My name is Jaroslav Tulach and I am the founder and initial architect of [[NetBeans]], which is not just a well known IDE, but also the first modular desktop ''application framework written in [[Java]]''. My name sounds Slavic and has a strange pronunciation (read the initial J as Y and last ch as Spanish J), because I am Czech. However, as [[NetBeans]] has been the flagship software product of [[Sun]] Microsystems for a while now, you don't have to worry that the content of the book might not be ''widely applicable'' and understandable.		My name is Jaroslav Tulach and I am the founder and initial architect of [[NetBeans]], which is not just a well known IDE, but also the first modular desktop ''application framework written in [[Java]]''. My name sounds Slavic and has a strange pronunciation (read the initial J as Y and last ch as Spanish J), because I am Czech. However, as [[NetBeans]] has been the flagship software product of [[Sun]] Microsystems for a while now, you don't have to worry that the content of the book might not be ''widely applicable'' and understandable.

-	This book is based on notes that I have collected over the last ten years, while designing and maintaining NetBeans ~~APIs~~ and transferring this knowledge to the rest of our developers. It is a journal from the heart of the NetBeans laboratory, describing 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'' enough to be ''useful'' for most software projects.	+	This book is based on notes that I have collected over the last ten years, while designing and maintaining [[NetBeans]] [[API]]s and transferring this knowledge to the rest of our developers. It is a journal from the heart of the [[NetBeans]] laboratory, describing 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'' enough to be ''useful'' for most software projects.

	Knowledge of proper API design is essential for the successful creation of 21st century software. Let [[TheAPIBook\|this book]] be your guide while exploring the big wide world of [[API]] design.		Knowledge of proper API design is essential for the successful creation of 21st century software. Let [[TheAPIBook\|this book]] be your guide while exploring the big wide world of [[API]] design.

	[[User:JaroslavTulach\|Jaroslav Tulach]]		[[User:JaroslavTulach\|Jaroslav Tulach]]

JaroslavTulach at 15:22, 12 August 2009

JaroslavTulach — Wed, 12 Aug 2009 15:22:33 GMT

←Older revision		Revision as of 15:22, 12 August 2009
Line 1:		Line 1:
	Dear Reader,		Dear Reader,

-	Maybe you are standing in a book store, holding this book in your hand, and asking yourself: "Should I buy it?" Here is your answer: If you have ever written code and handed it to someone else to let them compile their code against yours, the answer is: "You are ready to enter the API design world and this book will help you explore it."	+	Maybe you are standing in a book store, holding this book in your hand, and asking yourself: "Should I buy it?" Here is your answer: If you have ever written code and handed it to someone else to let them compile their code against yours, 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 API design in five easy lessons". It cannot be read in "only three days!". If you are looking for a quick handbook, probably this book is not for you. On the other hand, if you are interested in a deeper knowledge of API design, in knowing not only the ''how'', but also the ''why'', let me introduce myself to you before you put this book back on the shelf.	+	However, this book does not attempt to "teach [[API]] design in five easy lessons". It cannot be read in "only three days!". If you are looking for a quick handbook, probably this book is not for you. On the other hand, if you are interested in a deeper knowledge of [[API]] design, in knowing not only the ''how'', but also the ''why'', let me introduce myself to you before you put this book back on the shelf.

-	My name is Jaroslav Tulach and I am the founder and initial architect of NetBeans, which is not just a well known IDE, but also the first modular desktop ''application framework written in Java''. My name sounds Slavic and has a strange pronunciation (read the initial J as Y and last ch as Spanish J), because I am Czech. However, as NetBeans has been the flagship software product of Sun Microsystems for a while now, you don't have to worry that the content of the book might not be ''widely applicable'' and understandable.	+	My name is Jaroslav Tulach and I am the founder and initial architect of [[NetBeans]], which is not just a well known IDE, but also the first modular desktop ''application framework written in [[Java]]''. My name sounds Slavic and has a strange pronunciation (read the initial J as Y and last ch as Spanish J), because I am Czech. However, as [[NetBeans]] has been the flagship software product of [[Sun]] Microsystems for a while now, you don't have to worry that the content of the book might not be ''widely applicable'' and understandable.

-	This book is based on notes that I have collected over the last ten years, while designing and maintaining NetBeans APIs and transferring this knowledge to the rest of our developers. It is a journal from the heart of the NetBeans laboratory, describing 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'' enough to be ''useful'' for most software projects.	+	This book is based on notes that I have collected over the last ten years, while designing and maintaining NetBeans APIs and transferring this knowledge to the rest of our developers. It is a journal from the heart of the NetBeans laboratory, describing 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'' enough to be ''useful'' for most software projects.

-	Knowledge of proper API design is essential for the successful creation of 21st century software. Let this book be your guide while exploring the big wide world of API design.	+	Knowledge of proper API design is essential for the successful creation of 21st century software. Let [[TheAPIBook\|this book]] be your guide while exploring the big wide world of [[API]] design.

	[[User:JaroslavTulach\|Jaroslav Tulach]]		[[User:JaroslavTulach\|Jaroslav Tulach]]

192.9.112.196 at 14:31, 11 August 2008

192.9.112.196 — Mon, 11 Aug 2008 14:31:04 GMT

←Older revision		Revision as of 14:31, 11 August 2008
Line 1:		Line 1:
	Dear Reader,		Dear Reader,

-	Maybe you are standing in a book store, holding this book in your hand, and 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 code against yours, the answer is: "You are ready to enter the API design world and this book will help you explore it."	+	Maybe you are standing in a book store, holding this book in your hand, and asking yourself: "Should I buy it?" Here is your answer: If you have ever written code and handed it to someone else to let them compile their code against yours, 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 API design in five easy lessons". It cannot be read in "only three days!". If you are looking for a quick handbook, probably this book is not for you. On the other hand, if you are interested in a deeper knowledge of API design, in knowing not only the ''how'', but also the ''why'', let me introduce myself to you before you put this book back on the shelf.		However, this book does not attempt to "teach API design in five easy lessons". It cannot be read in "only three days!". If you are looking for a quick handbook, probably this book is not for you. On the other hand, if you are interested in a deeper knowledge of API design, in knowing not only the ''how'', but also the ''why'', let me introduce myself to you before you put this book back on the shelf.

192.9.112.196 at 14:14, 11 August 2008

192.9.112.196 — Mon, 11 Aug 2008 14:14:44 GMT

←Older revision		Revision as of 14:14, 11 August 2008
Line 5:		Line 5:
	However, this book does not attempt to "teach API design in five easy lessons". It cannot be read in "only three days!". If you are looking for a quick handbook, probably this book is not for you. On the other hand, if you are interested in a deeper knowledge of API design, in knowing not only the ''how'', but also the ''why'', let me introduce myself to you before you put this book back on the shelf.		However, this book does not attempt to "teach API design in five easy lessons". It cannot be read in "only three days!". If you are looking for a quick handbook, probably this book is not for you. On the other hand, if you are interested in a deeper knowledge of API design, in knowing not only the ''how'', but also the ''why'', let me introduce myself to you before you put this book back on the shelf.

-	My name is Jaroslav Tulach and I am the founder and initial architect of NetBeans, which is not just a well known IDE, but also the first modular desktop ''application framework written in Java''. My name sounds Slavic and has a strange pronunciation (read the initial J as Y and last ch as Spanish J), because I am Czech. However, as NetBeans has been the flagship software product of Sun Microsystems for a while now, you don't have to worry that content of the book might not be ''widely applicable'' and understandable.	+	My name is Jaroslav Tulach and I am the founder and initial architect of NetBeans, which is not just a well known IDE, but also the first modular desktop ''application framework written in Java''. My name sounds Slavic and has a strange pronunciation (read the initial J as Y and last ch as Spanish J), because I am Czech. However, as NetBeans has been the flagship software product of Sun Microsystems for a while now, you don't have to worry that the content of the book might not be ''widely applicable'' and understandable.

	This book is based on notes that I have collected over the last ten years, while designing and maintaining NetBeans APIs and transferring this knowledge to the rest of our developers. It is a journal from the heart of the NetBeans laboratory, describing 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'' enough to be ''useful'' for most software projects.		This book is based on notes that I have collected over the last ten years, while designing and maintaining NetBeans APIs and transferring this knowledge to the rest of our developers. It is a journal from the heart of the NetBeans laboratory, describing 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'' enough to be ''useful'' for most software projects.