Leaky abstractions
From APIDesign
(Difference between revisions)
| Line 1: | Line 1: | ||
| - | When creating an [[API]] one is creating a facade, an abstractions over the internals of the [[API]]'s implementation. Often the characteristics of the implementations are visible through the [[API]]. This is common source of [[wikipedia::Leaky | + | When creating an [[API]] one is creating a facade, an abstractions over the internals of the [[API]]'s implementation. Often the characteristics of the implementations are visible through the [[API]]. This is common source of [[wikipedia::Leaky abstraction|software bugs]]. |
Leakages of this kind are not restricted just to the world of [[API]]. After writing [[TheAPIBook]] I also noticed that I made my own [[LeakingCulturalContext|cultural context leak]] which created an unwanted confusion. | Leakages of this kind are not restricted just to the world of [[API]]. After writing [[TheAPIBook]] I also noticed that I made my own [[LeakingCulturalContext|cultural context leak]] which created an unwanted confusion. | ||
Revision as of 07:18, 31 October 2009
When creating an API one is creating a facade, an abstractions over the internals of the API's implementation. Often the characteristics of the implementations are visible through the API. This is common source of software bugs.
Leakages of this kind are not restricted just to the world of API. After writing TheAPIBook I also noticed that I made my own cultural context leak which created an unwanted confusion.
Follow
