Throughout my career I found that there is a limited amount of levels you can climb as a technical person. This sounds unfair, especially in companies that pride themselves on being technical. The earlier you are in your career, the more annoying this seems.
Design is hard—that’s what I hear from design leaders at every company I visit. As the VP of Design Education at InVision, I study how design works and breaks in businesses.
For over a year, the React team has been working to implement asynchronous rendering. Now we’d like to share with you some of the lessons we’ve learned while working on these features, and some recipes to help prepare your components for async rendering when it launches.
You probably don't need a Redis-backed background job system in your Elixir application. Here are some approaches to solving the problem of asynchronous work.
The web is a medium that has a viewport. What does it mean to truly be designing for the web — a medium that reveals the page slowly, from inside a viewport frame?
We've come quite far from where we started, and I was asked if I could give a talk to summarize what we've learned in the last 2 years as a set of native developers using React Native.
For the last 2 months, I've been working with ARKit on a replacement for our View in Room feature on modern iOS devices to support a "View in My Room". I'm going to try cover how we approached the project, the abstractions we created and give you a run through of how it works.
That project was the result of my desire to build a non-trivial program with WebAssembly, and get an early understanding of the challenges that pop up when integrating with existing web tools. Now that the emulator has grown to the point where I can actually play games, I figure it’s time to share a bit about what I learned.