Recently, QA reported two issues that which seems a little weird. After some investigations, I found they’re caused by my lack of knowledge of Ember Data APIs.

Redux is very popular in recent two years, it seems like it has become the standard architecture in React application.

Let’s compare it with original Flux.

In the latter half of last year, after I created a simple books searching demo via React + Flux + Immutable.js (I also mentioned it in last two articles), I have really fallen in love with unidirectional data flow as also the amazing technology stack.

In previous article, we got a general understanding about Flux architecture. And in Best Practise section, I have mentioned Immutable data which I haven’t take a look yet. Now it’s time to dig into it.

At the end of last year, there are two interesting stuff produced by Facebook came into fashion. One is React, another is Flux.

As a F2E (Front End Engineer), there is a big headache that how should I explain to others what is F2E or what F2E do.

Record some basic Git commands here for later reference.

In some javascript frameworks (Backbone, Ember, Angular, etc.), there is Router, which provide us ability to manage states in our applications.

Ember.js has been used in our application, and this week, I picked up a task to render a list, which seems very simple.

meaning is a mini blogging platform inspired by MEAN.JS(MongoDB, Express, AngularJS, and Node.js), and I will take notes here about how I deploy it on Amazon EC2.

When I built up this blog via hexo and themed it via noderce, I found there was a bug on UI – The footer of the page wasn’t stuck to the bottom because of the thin on content.

Just few days ago, when I wanna implement row stripping in a table, I still add class='odd' to alternative rows via javascript, and give the color in the css class. It’s a little bit sad for a F2E. :(

Hello, hexo.