Blog
We recently released our JavaScript Development Guidelines. This post explains how and why we developed them.
Last week eight members of our team spent three days at ng-conf where we were a Platinum Sponsor this year. Nick and I gave a talk at the Hack Night on Wednesday which seems to have resonated with a lot of people.
Above is every shape you need to draw in order to master the art of sketching amazing user interfaces (UI). A circle, a square, and a triangle. That’s it.
One of the largest process problems in building single page applications with AngularJS, React or Backbone is safely maintaining the contract between the AngularJS application and the REST API.
No contractors. Face-to-face teams in the same office. Integrated design and development. Frequent delivery. Validated UX. The application becomes the core design element. This is how we roll at rangle.io, with an intense real-time fusion of design and development. We haven't been talking about it enough, and I'm embarrassed to admit we've been under-representing our amazing design team on our website... something that we will be fixing in short order.
Here's the second JavaScript Teaser in our series for JavaScript ninjas. Can you figure it out? Please email Yuri if you want feedback on your answer. Do also let us know your thoughts on the question below (but don't post the answers in the comments section this time, so more people can send answers in.) Thanks!
Any non-trivial JavaScript requires dealing with asynchronicity. JavaScript can't wait, so if something that you want is not available right away, your code can't just sit around until the result comes back. Instead, the baseline solution is a callback: you provide a function that will be called when there result is either available or the operation is known to have failed.
At rangle.io we’ve been fans of the functional programming style for a while and have used Underscore and Lodash extensively on many projects. However, recently we started using a new library, Ramda, that on the surface seems very similar to Underscore, but which turns out to be different in a small but significant way. Ramda offers roughly the same set of methods as Underscore, but the way it offers them makes functional composition easy.