DePippo Blog

Chronicling my adventures in code

Using 'strict' mode in Javascript

There are a number of benefits to using ‘strict’ mode in Javascript. In general, these fall under the umbrella of better and more predictable error handling. Strict mode alerts us to potential problems in our code that might otherwise have gone unnoticed. Let’s take a look at some of the most significant examples of how strict mode differs from default Javascript.

Understanding closures in Javascript

In my last blog post, I used an interview question I’d recently been asked as a jumping off point to talk about data-binding. I’d like to do something similar this week, this time taking my cue from a question about Javascript closures. It’s another concept that is important to understand for Javascript developers, and is also likely to come up in technical interviews. So, what is a closure in Javascript?

Two-way data binding vs. One-way data flow

In a recent technical interview, I was asked to discuss the difference between two-way data binding and one-way data flow. From what I gather, this has become a fairly common interview question, and beyond that, I think it’s just an important concept to understand as a developer.

Using the Foursquare API with Angular

I recently came across an article – it’s a few years old now, but still relevant I think – about how a very wide swath of the internet relies on data from the Foursqaure API: In addition to the wealth of data it offers, a big part of what makes the Foursqaure API so appealing to me is its excellent documentation. I spent some time working with the API and integrating it with an Angular app, so I’d like to walk through my process.

Creating an Angular SPA with a Rails Backend

I recently wrote a Single Page App (SPA) called Vegan Food Finder, which features an Angular frontend and a Rails backend. It was a somewhat lengthy and involved process, but for the purposes of this blog entry, I’d like to focus specifically on how I got Angular communicating with my Rails backend.