He's going to work on Google Now, which is (more or less) the same thing I was working on with my previous employer. I could complain about how they are making

He's going to work on Google Now, which is (more or less) the same thing I was working on with my previous employer. I could complain about how they are making a worse version of what we did, but I'm not going to do that. I'm just glad people are starting to see the usefulness of location-based development. You may want to consider it from that perspective. People are getting interested in client-side frameworks. You laid important groundwork for that. Why not be happy about that? There will always be a cycle of change in software development. Trust me, you will not find that this pattern changes switching from front-end JS work to backend "native" programming work. The only constant in this world is constant change. If I was not satisfied with that, I would be into something like architectural engineering. When you build a bridge over a river, it lasts for hundreds of years. That said, I like a lot of the points in the article. I too have noted the absurdity of people complaining about how a 49kb file is "too large". I share the profound confusion of the hyper-simplicity movement, where we trade ~30kb of code for our ability to maintain software, which is a much bigger problem than performance in our industry today.