Why Github API is the best friend of developers

Why Github API is the best friend of developers
Why Github API is the best friend of developers


It was launched early in 2008 and has, since then, become an indispensable tool for many developers. In fact, eight years later, Github has 14 million users and 35 million repositories, as revealed by the company itself last April.

The repository hosting platform has thus established itself as the website par excellence within the current development scene when it comes to dealing with one of the key aspects of the creation of any software type and, more specifically, of an API: source code control, thanks to which one can create a more efficacious and efficient tool that can react to all possible situations.

Traditionally, source code control has been synonymous with managing the different files a development project is composed of. This not only means creating a hierarchical file system but also being able to store the different versions of the code, thus maintaining an historical record with which to explore and reverse an unsuccessful change. Ultimately, it entails being able to give continuity to the development, it being possible to recover previous versions without renouncing one’s efforts to try to effect modifications while attempting to find improvements.

Github’s success among API creators is due, for a start, to the fact that it makes it possible to carry out a quality collaborative task. Team development may seem to be incompatible with a strict control of the source code and the various versions made of it, but this is not the case with the repository hosting platform: whenever a collaborator of the project makes a change to the source code, this modification is shown as a revision of which its creator is responsible, as it appears directly linked to his or her user account, and which can be easily eliminated. 

Besides, this collaborative environment finds another great advantage in Github: code developing in its platform is agile. The fact that the founders of this service were three developers was undoubtedly influential when it came to creating a truly useful tool for code professionals. 

Still, developers do not live by group projects alone. For those who work with their own team on private tools, Github also offers a unique characteristic that has now become indispensable for corporative development: the integrated issue-tracking system.

Thanks to this, any failure or error of the source code can be marked with a kind of ticket with which to classify them all according to their longevity or number of comments. As explained by people from the platform itself, “your project’s issues page can be as simple or as sophisticated as you like. Filter by open and closed issues, assignees, labels…” In other words, we are dealing with a tool that will make problem-solving easier for small teams, who will be able to distribute the various tasks and the tracking among themselves.

Another of Github’s advantages is that it does not censure any programming language whatsoever. It accepts them all, without any restrictions or contradictions: it matters little that your API Project is being developed in an experimental or minority language; it will be accepted in Github without any problem.  

It is ultimately an organised community that follows one single methodology (by virtue of having the same development tools) and in which creativity flows easily. 

If you want to learn more about BBVA’s open platform and financial APIs, go to this site

It may interest you