Replacing RSpec controller specs, part 1: Request specs etc.

Does your application's test suite rely heavily on controller specs? It's time to consider alternatives, as controller testing has changed in Rails 5. Here's one way to replace a common use of these specs, even if you haven't upgraded to Rails 5 yet.

In Rails 5 autoloading is disbaled after booting the app in production mode by default

Code is communication. It has two audiences: the computer, and the future maintainer. How we communicate with the computer is rather objective: you either gave it the instructions to do what you really wanted, or you didn't.

In this talk, Carl Crawford (@StickyCarl) gives a whirlwind tour of the more popular and useful libraries available to React developers. This talk was filmed at JS Monthly London on July 25 2016. [00:00:05] I’m Carl. I’m a full-time developer at Sticky World. I like cats. Before that I was researching optimisation for dynamic initialisation. […]

Let's consider a hypothetical situation — You've been working on a Rails application for about a year. When the application was new and its functionality limited, you could add features relatively simply by spinning up a new controller, model and view or — worst case — add a few lines to an existing controller, model or view.

Rails 5 gives finer control over HSTS header and has cleaned up options for using SSL

HTTP/2 has some really amazing changes to the way web sites and applications can be built. A year and a half after becoming published, almost 10% of websites support HTTP/2. It has definitely had notable adoption, but the conversation should be pushed further for front-end developers on best practices when using HTTP/2. This is a multi-part blog post to give front-end developers a guide on how to switch over to HTTP/2.