avatarBirat Rai

Free AI web copilot to create summaries, insights and extended knowledge, download it at here

1824

Abstract

s usage has the path of least resistance.</li><li><b>Hard to use incorrectly</b>: Good API should make it difficult — ideally impossible — to use it incorrectly. API should be flexible to correct the mistakes done by the users, for example, an API might eliminate argument-ordering problems by allowing parameters to be passed in any order.</li></ul><p id="7144" type="7">TL;DR API should be easy to use and hard to use incorrectly.</p><p id="a0c3"><a href="https://readmedium.com/97-journey-every-programmer-should-accomplish-a0c53dbbfd47"><i>Go to the series</i></a>.</p><div id="10b2" class="link-block"> <a href="https://readmedium.com/97-journey-every-programmer-should-accomplish-a0c53dbbfd47"> <div> <div> <h2>97 Journey Every Programmer should Accomplish</h2> <div><h3>“A journey of a thousand miles begins with a single step.”</h3></div> <div><p>medium.com</p></div> </div> <div> <div style="background-image: url(https://miro.readmedium.com/v2/resize:fit:320/1*ImU1JEXOUUKMJxBF_OP-_w.png)"></div> </div> </div> </a> </div><p id="d42c">Go to <a href="https://readmedium.com/step-54-the-longevity-of-interim-solutions-klaus-marquardt-6521c820cddd"><b><i>54th Step</i></b></a></p><div id="60d0" class="link-block"> <a href="https://readmedium.com/step-54-the-longevity-of-interim-solutions-klaus-marquardt-6521c820cddd"> <div> <div> <h2>Step 54: The Longevity of Interim Solutions ~ Klaus Marquardt</h2> <div><h3>This is the 54th Step towards gaining the Programming Enlightenment series. If you didn’t learn the 53rd Step, read it.</h3></div> <div><p>medium.co

Options

m</p></div> </div> <div> <div style="background-image: url(https://miro.readmedium.com/v2/resize:fit:320/)"></div> </div> </div> </a> </div><p id="39c4">Go to the <b><i>56th Step</i></b>.</p><div id="b3d6" class="link-block"> <a href="https://readmedium.com/step-56-make-the-invisible-more-visible-jon-jagger-b54756c03976"> <div> <div> <h2>Step 56: Make the Invisible More Visible ~ Jon Jagger</h2> <div><h3>This is the 56th Step towards gaining the Programming Enlightenment series. If you didn’t learn the 55th Step, read it.</h3></div> <div><p>medium.com</p></div> </div> <div> <div style="background-image: url(https://miro.readmedium.com/v2/resize:fit:320/)"></div> </div> </div> </a> </div><blockquote id="ba78"><p><b>References:</b></p></blockquote><ul><li><a href="https://www.gitbook.com/book/97-things-every-x-should-know/97-things-every-programmer-should-know/details"><i>97 things Every Programmer Should Know</i></a> ~ Git Book</li><li><a href="https://www.amazon.com/Things-Every-Programmer-Should-Know/dp/0596809484"><i>97 Things Every Programmer Should Know</i></a> ~ Paperback</li><li><a href="https://medium.freecodecamp.org/what-is-an-api-in-english-please-b880a3214a82"><i>What is an API</i></a><i>? ~ Medium</i></li><li><a href="https://stackoverflow.com/questions/3996651/what-is-compiler-linker-loader"><i>What is Linker, Compiler, Loader</i></a>? ~ Stackoverflow</li><li><a href="https://github.com/dogriffiths/HeadFirstAndroid/wiki/How-Android-Apps-are-Built-and-Run"><i>How Android app is built</i></a>? ~ github</li></ul></article></body>

Step 55: Make Interfaces Easy to Use Correctly and Hard to Use Incorrectly ~ Scott Meyers

This is the 55th Step towards gaining the Programming Enlightenment series. If you didn’t learn the 54th Step, read it.

img. source

What is API?

In computer programming, an API(Application Programming Interface) is a set of subroutine definitions, communication protocols, and tools for building software.

API makes it easier for developers to use certain technologies in building applications. It simplifies by abstracting the underlying implementation and exposing what the developer needs.

An API may be fore web-based system, operating system, database system, computer hardware or software library.

Why design API?

API’s are designed to be used by end users or developers. They must be a pleasure to use and will boost other’s productivity.

What is a good API design?

Good API design must be:

  • Easy to use correctly: People use API to solve their problems. The API’s should be designed so that it’s usage has the path of least resistance.
  • Hard to use incorrectly: Good API should make it difficult — ideally impossible — to use it incorrectly. API should be flexible to correct the mistakes done by the users, for example, an API might eliminate argument-ordering problems by allowing parameters to be passed in any order.

TL;DR API should be easy to use and hard to use incorrectly.

Go to the series.

Go to 54th Step

Go to the 56th Step.

References:

API
Programming
Software Development
Java
Coding
Recommended from ReadMedium