How does one design and develop for the responsive web? A lot of methodologies out there try to tackle this problem, but all of them rely on the same classic website development process. It boils down to the following: design and then develop. Let’s go nuts and flip this outdated methodology on its head.

It's important to understand that the APIs of the iOS SDK are written in Objective-C. Swift was designed to be compatible with these APIs. Based on past failures, Apple understood that Swift needed to be able to hook into the iOS SDK without having to rewrite every single API in Swift.

Canvas is little more than a glorified image tag, a sandbox for art. While immensely useful for dynamic animations you see in visualizations and games, it’s not accessible at all. It’s a pile of pixels, a locked box without any DOM for screen readers to walk.

Slow is relative. Slow is not a metric. In order to effectively measure our systems, we need metrics.This is why baselines for our systems are so essential.

Switching to a microservices architecture creates exciting opportunities in the marketplace for companies. For system architects and developers, it promises an unprecedented level of control and speed as they deliver innovative new web experiences to customers. But at such a breathless pace, it can feel like there’s not a lot of room for error. In the real world, you can’t stop developing and deploying your apps as you retool the processes for doing so. You know that your future success depends on transitioning to a microservices architecture, but how do you actually do it?

Fun is more productive. Fun leads to a better understanding of the problem domain. And that leads to fast code, even if it might be orders of magnitude away from optimal when viewed through a microscope.

Closures are extremely valuable if you know how to use them. The problem is that many JavaScript developers don't know how to use them. After reading this guide I hope you will have a good grasp of what a closure is, how it works, and when to use them.

Bug tracking is a process used by quality assurance personnel and programmers to keep track of software problems and resolutions.