If you are into JavaScript Engineering / Front End Development (and chances are very high that you “are” if you are reading this) you must have realized that every year things evolve exponentially faster than the former one. In the year 2012, so many awesome articles, tools and resources were …

It has been almost a year since I wrote about interviews. In that time frame I’ve learned a lot. Furthermore, I’ve learned most of the things the hard way. I also realized that most of the interviewing books, articles and blog posts are completely and utterly misdirections, to say the …

In the former article of the series We rendered the user interface of our widget inside an anchor element in publisher’s website; We asynchronously loaded widget styles; We implemented a very naive authentication mechanism. We also defined a job queue _wdq (similar to google analytics’ _gaq) to be able to …

After my conference on jstanbul 2012, I updated the presentation adding some bullet points for the questions and feedback from the community.     You can view and download the presentation from SlideShare. And I’ll continue this blog’s series on JavaScript Widget Development Best Practices from where I left. Until …

I’m giving a talk on JavaScript Widget development best practices tomorrow at jstanbul 2012. At the conference, I will have a 30-minute timeframe to express as much as I can with respect to external JavaScript widget development best practices. Since 30 minutes is not enough for this, my aim is …

In the former part of the series we’ve seen how to revalidate the cache and load our widget code using a self updating bootloader script. Now it’s time to pass initialization parameters to our widget, and request some state data from the widget API server. Let’s recap: Our lovely publisher …

In the former post we have outlined a broad brushstrokes initialization flow of our external JavaScript Widget: What we did was to basically create a bootloader script that first loaded required resources asynchronously and then continued its flow with the initialization and rendering of the widget. Currently, those initialization and …

In the former part of the series we had a brief introduction on challenges in developing JavaScript widgets. In this article, we’re going to continue from where we left: We will start by installing necessary instruments to develop and test our code. First Things First Before we start actual coding, …

This is the beginning of a new article series where we will see best practices, common pitfalls, and “how to”s on creating JavaScript Widgets for external sites. Throughout the examples we will be using: node.js for the server; On top of node, expres.js framework as a higher-level abstraction; mongodb for …

Unless you have been living in a cave for the recent two years, you should known that node.js is a highly efficient platform built on Chrome’s JavaScript runtime for easily building fast, scalable network applications, by using an event-driven, non-blocking I/O model. node.js is lightweight and efficient; perfect for data-intensive …