Main Page

From APIDesign

Revision as of 14:20, 15 December 2012 (edit) Timmyevans (Talk | contribs) ← Previous diff		Current revision (11:32, 24 February 2017) (edit) (undo) Apidesign (Talk | contribs)
(4 intermediate revisions not shown.)
Line 1:		Line 1:
-	Dos And Don'ts Of Running A Business	+	[[I]] created this [[Main Page|website]] when the [[TheAPIBook|Practical API Design]] book (describing all the design mistakes [[I]] did when designing [[NetBeans]]) was published to be a source of latest on-line news from the world of API Design. I still publish my observations about [[APIDesignPatterns]] or various [[APITypes]], but [[I]] am also trying to cover other projects of mine like [[Bck2Brwsr]] or [[DukeScript]]. Here is the overview of most recent topics that [[I]] [[blogs|blogged]] about:
-	The goal to all business is turning a profit, but exactly how to do so is another matter. The truth is there are no real simple answers, but there are guidelines that offer the promise of success. Some things depend on the scope of the business, and what the business owner is capable of doing.	+	<rss desc=off number=5 >http://wiki.apidesign.org/index.php?title=Blogs:JaroslavTulach:Theory&action=feed&feed=rss|http://wiki.apidesign.org/index.php?title=Blogs:JaroslavTulach:Practical_Design&action=feed&feed=rss|http://wiki.apidesign.org/index.php?title=Blogs:JaroslavTulach:Daily_Life&action=feed&feed=rss</rss>
-	Good Habits for Profit	+	Anyway I'll be thankful if you decide to read the [[TheAPIBook|Practical API Design]] book. Here is few reasons why to do it: [[Have You Ever Wondered]]?
-	This is not an exhaustive list, and there will be many variations offered by different sources. The following will give a basic idea of ways get your business into the customer base building mode:	+	[[Image:Apidesign.jpg|link=http://practical.apidesign.org]]
-	Putting the right gear in place: No business can succeed without the necessary implements of the trade. Computers and various types of meeting software are pretty much basic essentials these days. However, other solutions that are fast becoming must haves include web conferencing tools, smart phones and Internet based promotional tools.	+	There are people who found [[TheAPIBook|Practical API Design]] too philosophical. For those, I've decided to follow steps of previous [[wikipedia:Kant|misunderstood philosopher]]s and released shorter summary: [[20 API Paradoxes]] (for dummies). In this book I concentrated on the most critical question: '''What is the difference between classical day-to-day programming and designing a framework'''? In the past I'd collected at least twenty of such differences, and because they are a bit surprising, I call them [[paradox]]es. In case you prefer just the final ''advice'', and don't care that much about the ''journey'' (e.g. philosophy), consider [[20 API Paradoxes]].
-	The customer is always right: It may sound like a tired refrain to say that the customer always come first, but this adage is still true today. Always be willing to listen to your customers. And be prepared to go the extra mile for those that arent quite satisfied, that is, if you didnt deliver as promised.	+	{{:Paradoxes}}
-		+
-	Upgrade your skills: There is always something new to learn in just about any field. The smart business owner keeps abreast of changes in their area so they can keep offering quality service.	+
-		+
-	Network, network: There are so many opportunities for building vital links for your business. These include trade shows and expos, family gatherings and high school reunions. This simply means letting others know what you do in order to create your own opportunities.	+
-		+
-	Business owners can add to this list as they see fit. This is a useful guide that can serve as a springboard to profitability. Many businesses choose to promote themselves online as it is more cost effective. The boom in support software for customer support and smart phone use underscores the need for fast and reliable communications. Keep in mind that if you ignore the basics of good business habits, you can be sure your competitor wont.	+

---

Current revision

I created this website when the Practical API Design book (describing all the design mistakes I did when designing NetBeans) was published to be a source of latest on-line news from the world of API Design. I still publish my observations about APIDesignPatterns or various APITypes, but I am also trying to cover other projects of mine like Bck2Brwsr or DukeScript. Here is the overview of most recent topics that I blogged about:

Theory Feeling the Pain! The Genetics of an APIDesign The Science of APIDesign Adding DefaultMethods in a 100% BackwardCompatible Way! Never Update (API) Tests!

Practical Design Marketing Version Do not Expose Deep Hierarchies! Using record on any JDK! 2021: Code VSCode UI in Java Bck2Brwsr 0.50: Ready for 2021 Technologies

Apache Projects can Distribute GPLwithClassPathException components! Never forget to add GradleWrapper! Micronaut Brings Compile Time Annotations to JavaEE Developers Spreading Malware Twenty Years: Sun Microsystems Acquires NetBeans

Anyway I'll be thankful if you decide to read the Practical API Design book. Here is few reasons why to do it: Have You Ever Wondered?

There are people who found Practical API Design too philosophical. For those, I've decided to follow steps of previous misunderstood philosophers and released shorter summary: 20 API Paradoxes (for dummies). In this book I concentrated on the most critical question: What is the difference between classical day-to-day programming and designing a framework? In the past I'd collected at least twenty of such differences, and because they are a bit surprising, I call them paradoxes. In case you prefer just the final advice, and don't care that much about the journey (e.g. philosophy), consider 20 API Paradoxes.

Soon after publishing Kant's Critique of Pure Reason, Kant realized that nobody is able to read it all and he released his Prolegomena to summarize and re-explain in more understandable style the thoughts of his Critique. I'd like my Paradoxes to do the same to TheAPIBook with the hope to attract wider audience to the topic of API design and convince part of them that it is worth to buy TheAPIBook.

The book is now available for download at Amazon US and mirror sites, including Amazon GB. Those who prefer other formats and readers than kindle may take a look at Barnes & Noble site.

The presentation has been delivered many times. Here is a recording of 20 API Paradoxes at JDD Krakow.