I left the source of inspiration of [[TheAPIBook]] - I only contribute to the [[NetBeans]] [[Apache]] project in my spare time - as a result I had to find [[OracleLabs|another organization]] to feed me with [[APIDesign]] mistakes. It is a [[MidlifeCrisis|strong suply]], yet I believe the list of my [[TwoYearsWithTruffle|achievements in the recent years]] allows one conclusion: It is possible to design an [[API]] as a service! I wish the impact of the [[TheAPIBook|Practical API Design]] book has been bigger: It is clear there is a lot of people struggling to design an [[API]] and it would really help them to avoid inventing the wheel. Many of the [[TheAPIBook|Practical API Design]] observations would help to avoid the mistakes [[I]] am [[MidlifeCrisis|seeing all around]], but maybe it is [[TheAPIBook|not that easy to read]], maybe it is the [[Talkback|personalization]] that counts!

I left the source of inspiration of [[TheAPIBook]] - I only contribute to the [[NetBeans]] [[Apache]] project in my spare time - as a result I had to find [[OracleLabs|another organization]] to feed me with [[APIDesign]] mistakes. It is a [[MidlifeCrisis|strong suply]], yet I believe the list of my [[TwoYearsWithTruffle|achievements in the recent years]] allows one conclusion: It is possible to design an [[API]] as a service! I wish the impact of the [[TheAPIBook|Practical API Design]] book has been bigger: It is clear there is a lot of people struggling to design an [[API]] and it would really help them to avoid inventing the wheel. Many of the [[TheAPIBook|Practical API Design]] observations would help to avoid the mistakes [[I]] am [[MidlifeCrisis|seeing all around]], but maybe it is [[TheAPIBook|not that easy to read]], maybe it is the [[Talkback|personalization]] that counts!

Don't you need a skilled [[API]] designer? Don't you want to improve your [[API Design]] skills with a funny game-like [[Using_Games_to_Improve_API_Design_Skills|training]]? [[Talkback]] to [[I|me]]. Actively joining would be the best celebration of the 10th anniversary of the [[TheAPIBook|Practical API Design]] book!

Don't you need a skilled [[API]] designer? Don't you want to improve your [[API Design]] skills with an entertaining game-like [[Using_Games_to_Improve_API_Design_Skills|training]]? [[Talkback]] to [[I|me]]. Actively joining would be the best celebration of the 10th anniversary of the [[TheAPIBook|Practical API Design]] book!

[[ClarityOfTypes|Types]] went away and returned back. For a while it seemed that types were heading to unimportance with the decline of [[Java]]. It is true that the runtime characteristics of dynamic languages like [[JavaScript]] got on par over [[TenYears|the years]]. Yet, it seems the types are striking back: [[TypeScript]], [[Kotlin]], etc. show that for certain tasks (like designing an [[API]]) having a type is an advantage. While [[I]] am able to design an [[API]] in a dynamic language, having types makes it all more convenient and alike to advises described in [[TheAPIBook]].

[[ClarityOfTypes|Types]] went away and returned back. For a while it seemed that types were heading to unimportance with the decline of [[Java]]. It is true that the runtime characteristics of dynamic languages like [[JavaScript]] got on par over [[TenYears|the years]]. Yet, it seems the types are striking back: [[TypeScript]], [[Kotlin]], etc. show that for certain tasks (like designing an [[API]]) having a type is an advantage. While [[I]] am able to design an [[API]] in a dynamic language, having types makes it all more convenient and alike to advises described in [[TheAPIBook]].

I left the source of inspiration of [[TheAPIBook]] - I only contribute to the [[NetBeans]] [[Apache]] project in my spare time - as a result I had to find [[OracleLabs|another organization]] to feed me with [[APIDesign]] mistakes. It is a [[MidlifeCrisis|strong suply]], yet I believe the list of my [[TwoYearsWithTruffle|achievements in the recent years]] allows one conclusion: It is possible to design an [[API]] as a service! I wish the impact of the [[TheAPIBook|Practical API Design]] book has been bigger. It is clear there is a lot of people struggling to design an [[API]] and it would really help them to avoid inventing the wheel. Many of the [[TheAPIBook|Practical API Design]] observations would help to avoid the mistakes [[I]] am [[MidlifeCrisis|seeing all around]], but maybe it is [[TheAPIBook|not that easy to read]], maybe it is the [[Talkback|personalization]] that counts!

I left the source of inspiration of [[TheAPIBook]] - I only contribute to the [[NetBeans]] [[Apache]] project in my spare time - as a result I had to find [[OracleLabs|another organization]] to feed me with [[APIDesign]] mistakes. It is a [[MidlifeCrisis|strong suply]], yet I believe the list of my [[TwoYearsWithTruffle|achievements in the recent years]] allows one conclusion: It is possible to design an [[API]] as a service! I wish the impact of the [[TheAPIBook|Practical API Design]] book has been bigger: It is clear there is a lot of people struggling to design an [[API]] and it would really help them to avoid inventing the wheel. Many of the [[TheAPIBook|Practical API Design]] observations would help to avoid the mistakes [[I]] am [[MidlifeCrisis|seeing all around]], but maybe it is [[TheAPIBook|not that easy to read]], maybe it is the [[Talkback|personalization]] that counts!

Don't you need a skilled [[API]] designer? Don't you want to improve your [[API Design]] skills with a funny game-like [[Using_Games_to_Improve_API_Design_Skills|training]]? [[Talkback]] to [[I|me]]. Actively joining would be the best celebration of the 10th anniversary of the [[TheAPIBook|Practical API Design]] book!

Don't you need a skilled [[API]] designer? Don't you want to improve your [[API Design]] skills with a funny game-like [[Using_Games_to_Improve_API_Design_Skills|training]]? [[Talkback]] to [[I|me]]. Actively joining would be the best celebration of the 10th anniversary of the [[TheAPIBook|Practical API Design]] book!

Ten years ago, on July 29, 2008, the [[TheAPIBook|Practical API Design]] book was published. Isn't that a date to remember and celebrate? Yeah, it certainly deserves at least a little note. Many things has changed over the last [[TenYears|ten years]]...

[[TenYears|Ten years]] ago, on July 29, 2008, the [[TheAPIBook|Practical API Design]] book was published. Isn't that a date to remember and celebrate? Yeah, it certainly deserves at least a little note. Many things has changed over the last [[TenYears|ten years]]...

The language that I used for most of the examples, [[Java]], is no longer as popular as it used to be. It is no longer taught at basic university courses. It is no longer the choice of those who want to use [[good technology]] with all its three essential components (coolness, time to market and [[Cost of Ownership]]). Does that mean [[TheAPIBook]] content is no longer valid? Not that all! [[I]] always expected [[Java]] to evolve into something different - the language was just a tool - thus the core ideas still remain fresh and useful.

The language that I used for most of the examples, [[Java]], is no longer as popular as it used to be. It is no longer taught at basic university courses. It is no longer the choice of those who want to use [[good technology]] with all its three essential components (coolness, time to market and [[Cost of Ownership]]). Does that mean [[TheAPIBook]] content is no longer valid? Not that all! [[I]] always expected [[Java]] to evolve into something different - the language was just a tool - thus the core ideas still remain fresh and useful.

I left the source of inspiration of [[TheAPIBook]] - I only contribute to the [[NetBeans]] [[Apache]] project in my spare time - as a result I had to find [[OracleLabs|another organization]] to feed me with [[APIDesign]] mistakes. It is a [[MidlifeCrisis|strong suply]], yet I believe the list of my [[TwoYearsWithTruffle|achievements in the recent years]] allows one conclusion: It is possible to design an [[API]] as a service! I wish the impact of the [[TheAPIBook|Practical API Design]] book has been bigger. It is clear there is a lot of people struggling to design an [[API]] and it would really help them to avoid inventing the wheel. Many of the [[TheAPIBook|Practical API Design]] observations would help to avoid the mistakes [[I]] am [[MidlifeCrisis|seeing all around]], but maybe it is [[TheAPIBook|not that easy to read]], maybe it is the [[Talkback|personalization]] that counts!

I left the source of inspiration of [[TheAPIBook]] - I only contribute to the [[NetBeans]] [[Apache]] project in my spare time - as a result I had to find [[OracleLabs|another organization]] to feed me with [[APIDesign]] mistakes. It is a [[MidlifeCrisis|strong suply]], yet I believe the list of my [[TwoYearsWithTruffle|achievements in the recent years]] allows one conclusion: It is possible to design an [[API]] as a service! I wish the impact of the [[TheAPIBook|Practical API Design]] book has been bigger. It is clear there is a lot of people struggling to design an [[API]] and it would really help them to avoid inventing the wheel. Many of the [[TheAPIBook|Practical API Design]] observations would help to avoid the mistakes [[I]] am [[MidlifeCrisis|seeing all around]], but maybe it is [[TheAPIBook|not that easy to read]], maybe it is the [[Talkback|personalization]] that counts!

Don't you need a skilled [[API]] designer? Don't you want to improve your [[API Design]] skills with a funny game-like [[Using_Games_to_Improve_API_Design_Skills|training]]? [[Talkback]] to [[I|me]]. Actively joining would be the best celebrations of the 10th anniversary of the [[TheAPIBook|Practical API Design]] book!

Don't you need a skilled [[API]] designer? Don't you want to improve your [[API Design]] skills with a funny game-like [[Using_Games_to_Improve_API_Design_Skills|training]]? [[Talkback]] to [[I|me]]. Actively joining would be the best celebration of the 10th anniversary of the [[TheAPIBook|Practical API Design]] book!

[[ClarityOfTypes|Types]] went away and returned back. For a while it seemed that types were heading to unimportance with the decline of [[Java]]. It is true that the runtime characteristics of dynamic languages like [[JavaScript]] got on par over [[TenYears|the years]]. Yet, it seems the types are striking back: [[TypeScript]], [[Kotlin]], etc. show that for certain tasks (like designing an [[API]]) having a type is an advantage. While [[I]] am able to design an [[API]] in a dynamic language, having types makes it all more convenient and alike to advises described in [[TheAPIBook]].

[[ClarityOfTypes|Types]] went away and returned back. For a while it seemed that types were heading to unimportance with the decline of [[Java]]. It is true that the runtime characteristics of dynamic languages like [[JavaScript]] got on par over [[TenYears|the years]]. Yet, it seems the types are striking back: [[TypeScript]], [[Kotlin]], etc. show that for certain tasks (like designing an [[API]]) having a type is an advantage. While [[I]] am able to design an [[API]] in a dynamic language, having types makes it all more convenient and alike to advises described in [[TheAPIBook]].

I left the source of inspiration of [[TheAPIBook]] - I only contribute to the [[NetBeans]] [[Apache]] project in my spare time - as a result I had to find [[OracleLabs|another organization]] to feed me with [[APIDesign]] mistakes. It is a [[MidlifeCrisis|strong suply]], yet I believe the list of my [[TwoYearsWithTruffle|achievements in the recent years]] allows one conclusion: It is possible to design an [[API]] as a service! I wish the impact of the [[TheAPIBook|Practical API Design]] book has been bigger. It is clear there is a lot of people struggling to design an [[API]] and it would really help them to avoid inventing the wheel. Many of the [[TheAPIBook|Practical API Design]] observations would help to avoid the mistakes [[I]] am [[MidlifeCrisis|seeing all around]], but maybe it is [[TheAPIBook|not that easy to read]], maybe it is the personalization that counts!

I left the source of inspiration of [[TheAPIBook]] - I only contribute to the [[NetBeans]] [[Apache]] project in my spare time - as a result I had to find [[OracleLabs|another organization]] to feed me with [[APIDesign]] mistakes. It is a [[MidlifeCrisis|strong suply]], yet I believe the list of my [[TwoYearsWithTruffle|achievements in the recent years]] allows one conclusion: It is possible to design an [[API]] as a service! I wish the impact of the [[TheAPIBook|Practical API Design]] book has been bigger. It is clear there is a lot of people struggling to design an [[API]] and it would really help them to avoid inventing the wheel. Many of the [[TheAPIBook|Practical API Design]] observations would help to avoid the mistakes [[I]] am [[MidlifeCrisis|seeing all around]], but maybe it is [[TheAPIBook|not that easy to read]], maybe it is the [[Talkback|personalization]] that counts!

Don't you need a skilled [[API]] designer? Don't you want to improve your [[API Design]] skills with a funny game-like [[Using_Games_to_Improve_API_Design_Skills|training]]? [[Talkback]] to [[I|me]]. Actively joining would be the best celebrations of the 10th anniversary of the [[TheAPIBook|Practical API Design]] book!

Don't you need a skilled [[API]] designer? Don't you want to improve your [[API Design]] skills with a funny game-like [[Using_Games_to_Improve_API_Design_Skills|training]]? [[Talkback]] to [[I|me]]. Actively joining would be the best celebrations of the 10th anniversary of the [[TheAPIBook|Practical API Design]] book!

[[ClarityOfTypes|Types]] went away and returned back. For a while it seemed that types were heading to unimportance with the decline of [[Java]]. It is true that the runtime characteristics of dynamic languages like [[JavaScript]] got on par over [[TenYears|the years]]. Yet, it seems the types are striking back: [[TypeScript]], [[Kotlin]], etc. show that for certain tasks (like designing an [[API]]) having a type is an advantage. While [[I]] am able to design an [[API]] in a dynamic language, having types makes it all more convenient and alike to advises described in [[TheAPIBook]].

[[ClarityOfTypes|Types]] went away and returned back. For a while it seemed that types were heading to unimportance with the decline of [[Java]]. It is true that the runtime characteristics of dynamic languages like [[JavaScript]] got on par over [[TenYears|the years]]. Yet, it seems the types are striking back: [[TypeScript]], [[Kotlin]], etc. show that for certain tasks (like designing an [[API]]) having a type is an advantage. While [[I]] am able to design an [[API]] in a dynamic language, having types makes it all more convenient and alike to advises described in [[TheAPIBook]].

I left the source of inspiration of [[TheAPIBook]] - I only contribute to the [[NetBeans]] [[Apache]] project in my spare time - as a result I had to find [[OracleLabs|another organization]] to feed me with [[APIDesign]] mistakes. It is a [[MidlifeCrisis|strong suply]], yet I believe the list of my achievements in the [[TwoYearsWithTruffle|recent years]] allows one conclusion: It is possible to design an [[API]] as a service! I wish the impact of the [[TheAPIBook|Practical API Design]] book has been bigger. It is clear there is a lot of people struggling to design an [[API]] and it would really help them to avoid inventing the wheel. Many of the [[TheAPIBook|Practical API Design]] observations would help to avoid the mistakes [[I]] am [[MidlifeCrisis|seeing all around]], but maybe it is [[TheAPIBook|not that easy to read]], maybe it is the personalization that counts!

I left the source of inspiration of [[TheAPIBook]] - I only contribute to the [[NetBeans]] [[Apache]] project in my spare time - as a result I had to find [[OracleLabs|another organization]] to feed me with [[APIDesign]] mistakes. It is a [[MidlifeCrisis|strong suply]], yet I believe the list of my [[TwoYearsWithTruffle|achievements in the recent years]] allows one conclusion: It is possible to design an [[API]] as a service! I wish the impact of the [[TheAPIBook|Practical API Design]] book has been bigger. It is clear there is a lot of people struggling to design an [[API]] and it would really help them to avoid inventing the wheel. Many of the [[TheAPIBook|Practical API Design]] observations would help to avoid the mistakes [[I]] am [[MidlifeCrisis|seeing all around]], but maybe it is [[TheAPIBook|not that easy to read]], maybe it is the personalization that counts!

Don't you need a skilled [[API]] designer? Don't you want to improve your [[API Design]] skills with a funny game-like [[Using_Games_to_Improve_API_Design_Skills|training]]? [[Talkback]] to [[I|me]]. Actively joining would be the best celebrations of the 10th anniversary of the [[TheAPIBook|Practical API Design]] book!

Don't you need a skilled [[API]] designer? Don't you want to improve your [[API Design]] skills with a funny game-like [[Using_Games_to_Improve_API_Design_Skills|training]]? [[Talkback]] to [[I|me]]. Actively joining would be the best celebrations of the 10th anniversary of the [[TheAPIBook|Practical API Design]] book!

[[ClarityOfTypes|Types]] went away and returned back. For a while it seemed that types were heading to unimportance with the decline of [[Java]]. It is true that the runtime characteristics of dynamic languages like [[JavaScript]] got on par over [[TenYears|the years]]. Yet, it seems the types are striking back: [[TypeScript]], [[Kotlin]], etc. show that for certain tasks (like designing an [[API]]) having a type is an advantage. While [[I]] am able to design an [[API]] in a dynamic language, having types makes it all more convenient and alike to advises described in [[TheAPIBook]].

[[ClarityOfTypes|Types]] went away and returned back. For a while it seemed that types were heading to unimportance with the decline of [[Java]]. It is true that the runtime characteristics of dynamic languages like [[JavaScript]] got on par over [[TenYears|the years]]. Yet, it seems the types are striking back: [[TypeScript]], [[Kotlin]], etc. show that for certain tasks (like designing an [[API]]) having a type is an advantage. While [[I]] am able to design an [[API]] in a dynamic language, having types makes it all more convenient and alike to advises described in [[TheAPIBook]].

I left the source of inspiration of [[TheAPIBook]] - I only contribute the [[NetBeans]] in my spare time - as a result I had to find [[OracleLabs|another organization]] to feed me with [[APIDesign]] mistakes. It is a [[MidlifeCrisis|strong suply]], yet I believe the list of my achievements in the [[TwoYearsWithTruffle|recent years]] allows one conclusion: It is possible to design an [[API]] as a service! I wish the impact of the [[TheAPIBook|Practical API Design]] book has been bigger. It is clear there is a lot of people struggling to design an [[API]] and it would really help them to avoid inventing the wheel. Many of the [[TheAPIBook|Practical API Design]] observations would help to avoid the mistakes [[I]] am [[MidlifeCrisis|seeing all around]], but maybe it is [[TheAPIBook|not that easy to read]], maybe it is the personalization that counts!

I left the source of inspiration of [[TheAPIBook]] - I only contribute to the [[NetBeans]] [[Apache]] project in my spare time - as a result I had to find [[OracleLabs|another organization]] to feed me with [[APIDesign]] mistakes. It is a [[MidlifeCrisis|strong suply]], yet I believe the list of my achievements in the [[TwoYearsWithTruffle|recent years]] allows one conclusion: It is possible to design an [[API]] as a service! I wish the impact of the [[TheAPIBook|Practical API Design]] book has been bigger. It is clear there is a lot of people struggling to design an [[API]] and it would really help them to avoid inventing the wheel. Many of the [[TheAPIBook|Practical API Design]] observations would help to avoid the mistakes [[I]] am [[MidlifeCrisis|seeing all around]], but maybe it is [[TheAPIBook|not that easy to read]], maybe it is the personalization that counts!

Don't you need a skilled [[API]] designer? Don't you want to improve your [[API Design]] skills with a funny game-like [[Using_Games_to_Improve_API_Design_Skills|training]]? [[Talkback]] to [[I|me]]. Actively joining would be the best celebrations of the 10th anniversary of the [[TheAPIBook|Practical API Design]] book!

Don't you need a skilled [[API]] designer? Don't you want to improve your [[API Design]] skills with a funny game-like [[Using_Games_to_Improve_API_Design_Skills|training]]? [[Talkback]] to [[I|me]]. Actively joining would be the best celebrations of the 10th anniversary of the [[TheAPIBook|Practical API Design]] book!

Ten years ago, on July 29, 2008, the [[TheAPIBook|Practical API Design]] book was published. Isn't that a date to remember and celebrate? Yeah, it certainly deserves at least a little note. Many things has changed over the last ten years...

Ten years ago, on July 29, 2008, the [[TheAPIBook|Practical API Design]] book was published. Isn't that a date to remember and celebrate? Yeah, it certainly deserves at least a little note. Many things has changed over the last [[TenYears|ten years]]...

The language that I used for most of the examples, [[Java]], is no longer as popular as it used to be. It is no longer taught at basic university courses. It is no longer the choice of those who want to use [[good technology]] with all its three essential components (coolness, time to market and [[Cost of Ownership]]). Does that mean [[TheAPIBook]] content is no longer valid? Not that all! [[I]] always expected [[Java]] to evolve into something different - the language was just a tool - thus the core ideas still remain fresh and useful.

The language that I used for most of the examples, [[Java]], is no longer as popular as it used to be. It is no longer taught at basic university courses. It is no longer the choice of those who want to use [[good technology]] with all its three essential components (coolness, time to market and [[Cost of Ownership]]). Does that mean [[TheAPIBook]] content is no longer valid? Not that all! [[I]] always expected [[Java]] to evolve into something different - the language was just a tool - thus the core ideas still remain fresh and useful.

Ten years ago, on July 29, 2008, the [[TheAPIBook|Practical API Design]] book was published. Isn't that a date to remember and celebrate? Yeah, may be it is. It certainly deserves at least a little note. Many things has changed over the last ten years...

Ten years ago, on July 29, 2008, the [[TheAPIBook|Practical API Design]] book was published. Isn't that a date to remember and celebrate? Yeah, it certainly deserves at least a little note. Many things has changed over the last ten years...

The language that I used for most of the examples, [[Java]], is no longer as popular as it used to be. It is no longer taught at basic university courses. It is no longer the choice of those who want to use [[good technology]] with all its three essential components (coolness, time to market and [[Cost of Ownership]]). Does that mean [[TheAPIBook]] content is no longer valid? Not that all! [[I]] always expected [[Java]] to evolve into something different - the language was just a tool - thus the core ideas still remain fresh and useful.

The language that I used for most of the examples, [[Java]], is no longer as popular as it used to be. It is no longer taught at basic university courses. It is no longer the choice of those who want to use [[good technology]] with all its three essential components (coolness, time to market and [[Cost of Ownership]]). Does that mean [[TheAPIBook]] content is no longer valid? Not that all! [[I]] always expected [[Java]] to evolve into something different - the language was just a tool - thus the core ideas still remain fresh and useful.

[[ClarityOfTypes|Types]] went away and returned back. For a while it seemed that types were heading to unimportance with the decline of [[Java]]. It is true that the runtime characteristics of dynamic languages like [[JavaScript]] got on par over [[TenYears|the years]]. Yet, it seems the types are striking back: [[TypeScript]], [[Kotlin]], etc. show that for certain tasks (like designing an [[API]]) having a type is an advantage. While [[I]] am able to design an [[API]] in a dynamic language, having types makes it all more convenient and alike to advises described in [[TheAPIBook]].

[[ClarityOfTypes|Types]] went away and returned back. For a while it seemed that types were heading to unimportance with the decline of [[Java]]. It is true that the runtime characteristics of dynamic languages like [[JavaScript]] got on par over [[TenYears|the years]]. Yet, it seems the types are striking back: [[TypeScript]], [[Kotlin]], etc. show that for certain tasks (like designing an [[API]]) having a type is an advantage. While [[I]] am able to design an [[API]] in a dynamic language, having types makes it all more convenient and alike to advises described in [[TheAPIBook]].

I left the source of inspiration of [[TheAPIBook]] - I only contribute the [[NetBeans]] in my spare time - as a result I had to find [[OracleLabs|another organization]] to feed me with [[APIDesign]] mistakes. It is a [[MidlifeCrisis|strong suply]], yet I believe the list of my achievements in the [[TwoYearsWithTruffle|recent years]] allows one conclusion: It is possible to design an [[API]] as a service! I wish the impact of the [[TheAPIBook|Practical API Design]] book has been bigger. It is clear there is a lot of people struggling to design an [[API]] and it would really help them to avoid inventing the wheel. Many of the [[TheAPIBook|Practical API Design]] observations would help to avoid the mistakes [[I]] am [[MidlifeCrisis|seeing all around]]. But maybe it is [[TheAPIBook|not that easy to read]], maybe it is the personalization that counts!

I left the source of inspiration of [[TheAPIBook]] - I only contribute the [[NetBeans]] in my spare time - as a result I had to find [[OracleLabs|another organization]] to feed me with [[APIDesign]] mistakes. It is a [[MidlifeCrisis|strong suply]], yet I believe the list of my achievements in the [[TwoYearsWithTruffle|recent years]] allows one conclusion: It is possible to design an [[API]] as a service! I wish the impact of the [[TheAPIBook|Practical API Design]] book has been bigger. It is clear there is a lot of people struggling to design an [[API]] and it would really help them to avoid inventing the wheel. Many of the [[TheAPIBook|Practical API Design]] observations would help to avoid the mistakes [[I]] am [[MidlifeCrisis|seeing all around]], but maybe it is [[TheAPIBook|not that easy to read]], maybe it is the personalization that counts!

Don't you need a skilled [[API]] designer? Don't you want to improve your [[API Design]] skills with a funny game-like [[Using_Games_to_Improve_API_Design_Skills|training]]? [[Talkback]] to [[I|me]]. Actively joining would be the best celebrations of the 10th anniversary of the [[TheAPIBook|Practical API Design]] book!

Don't you need a skilled [[API]] designer? Don't you want to improve your [[API Design]] skills with a funny game-like [[Using_Games_to_Improve_API_Design_Skills|training]]? [[Talkback]] to [[I|me]]. Actively joining would be the best celebrations of the 10th anniversary of the [[TheAPIBook|Practical API Design]] book!