All Posts
-
Double Agent Profile: Jessie Puls
Meet the double agents behind Test Double’s mission to build great software and great teams. In this edition, find out more about Jessie Puls. -
Using CockroachDB with Rails
CockroachDB is a scalable, highly available database, and you can use it in your Rails apps today. In this guide, we'll walk you through the steps to using CockroachDB with Rails. -
Double Agent Profile: Meri Brace
Meet the double agents behind Test Double’s mission to build great software and great teams. In this edition, find out more about Meri Brace. -
React Context for Dependency Injection Not State Management
Dive into the concept that React Context API is primarily a tool for injecting dependencies into a React tree and how we can use that to improve testability, reusability, and maintainability of our apps. -
Double Agent Profile: Landon Gray
Meet the double agents behind Test Double’s mission to build great software and great teams. In this edition, find out more about Landon Gray. -
Announcing Standard Ruby 1.0
After two years of community feedback and 80 releases, Standard Ruby hit 1.0 this week. Find out what's new and why there's never been a better time to standardize your app! -
Why privacy-minded analytics can fix marketing
Marketing is at fault for many data privacy issues. Privacy-minded analytics can fix what’s broken about marketing. And it’s also important to Test Double. -
Best Interview Process. Ever. Actually.
Newly minted Double Agent Nichol Alexander shares an outside perspective on Test Double’s senior software engineer interview process. -
There's No Such Thing as a Free Gem
If you had to connect your app to an OAuth provider, when would you rely on a library and when would you code it yourself? Could you explain your reasoning? Using OAuth log in to Twitter in Ruby on Rails as an example, let's walk through the decision to roll our own implementation and how to build it ourselves with working code samples. -
How to completely uninstall and reinstall Homebrew Postgres
Is Postgres erroring with "could not read block 39" or "bad address"? If you installed Postgres via Homebrew on a Mac, here's the quickest way to wipe the slate clean with a fresh install
1 of 13
