The javascript engineers have been troubled often with the callbacks and the callback hell. The rescue are the promises: an easy and convenient way to handle the asynchronous calls.

A promise is an alternative way which allows us to handle asynchronous operations in a more elegant way than callbacks

Let's assume a simple story which will help us understand this. (well OK, I know that its not the best example you've ever read)

A father asks his son to go and buy a newspaper. The father is awaiting for the newspaper and will start reading it when his son returns back. On the other hand, the father knows that his son, who loves playing out in the yard, has some possibilities to fall down and start crying. In this case he won't read his newspaper and he will have to care of his son.

There are two cases in the story; the father will read the newspaper. The father won't read the newspaper.

• What happens on a single part of JS code?
  
• Is the code interpreted or compiled?
• What is the variable shadowing?
• What is the variable hoisting?
• What are the closures

In the following slide presentation I will try to answer the aforementioned questions by showing what the JS engine does on a simple part of code
​
Javascript compilation - execution

* In the company that I work for, we have a ceremony, called DOJO, in which any employer can present his/her ideas about any subject he/she wants to share (though we are trying to be focused on technological stuff). As such, this slide presentation was one of our DOJOs

Recently I met the "pair programming" term, which refers to two developers working together in the same task. 
There are plenty ways for this to happen. The most common though is that a developer writes code, whereas  the other shares ideas.  

I have discussed with many developers that tend to be a sort of full stack developers and if you ask them about their position they reply that they are back-end developers. It seems that it exists an inexplicable reason of making the developers believe that back-end is 'harder' than the 'front-end' and of course the harder way, the better developer. (I am not fond of this idea).
Do what ever you want but be GOOD at it!

I found it interesting to start writing this article by explaining the wrong way of designing an angular application.
The so common way to design an application is to group your modules (controllers, routes, services, factories, directives etc). The controllers to be in a controllers.js file, the services to be in a services.js file and so on. None can say that this is a bad design, but you will notice in the near future that this is not a so maintainable design because it's hard to find and amend a route that is inside the routes.js file and this file has more than 100 routes. 

Before diving into details in the matter of full stack applications, I would like to point out the reasons that make me start searching of something like this. You might ask "something like what?" :).
Well, firstly I started experimented with angular generator for creating a single page application that would connected with a REST API. But what about if I wanted to make any heavily data manipulation or anything sensitive? In the other hand, I met NodeJs' sockets and I would probably wanted to use them in future. 
For avoiding combine express with angular in a later stage, I decided to do it from beginning. 

Recently I tentative started reading about nodeJs and despite it’s a new framework I’ve been excited of the ecosystem it already has. Isn’t hard to find of what you are looking for and the nodeJs.org itself is really helpful.

When I first saw nodeJs’ motto “Node.js is a platform built on Chrome’s JavaScript runtime for easily building fast, scalable network applications” I focused on “fast” and I immediately wanted to do some comparisons with .NET+IIS. 

For my comparison I used ab Apache Http Server benchmarking tool

I will come back soon with more results

Both of applications have identical pages. It is just 10000 list items that comes from mysql. In order to test only the application and not the database I am caching the results the first time they arrive.