Andrew Gatenby

Fast, extendable and respects your privacy

Web browser of choice: - Extendable - Open source - Cross platform - Great privacy tools

Simplifies setup of Docker local and production environments wonderfully. Docker Compose

Well, we already have jQuery in our stack, so we couldn't not have plain JS too. We will write most JS to use jQuery methods, but to improve client-side performance we'll typically defer jQuery loading in. So if there's some client-side operations that need to happen before jQuery is available, then vanilla JS is how we'll typically handle that. JavaScript

jQuery has been the basis of our front end JS for a number of years. The key part for us was that the amount of code saved by using jQuery methods, as opposed to writing out cross-browser compatible alternatives made it a no brainer. In recent years we've had to be clever in how we deliver jQuery on the websites, to ensure it's not render blocking and improve client-side performance but it's still a vital library. jQuery

All of our responsive wireframes that are used to build the front end of our clients' sites are built with HTML 5, so we can ensure the most efficient and up to date experience for their customers. HTML5

Apache is used as the HTTP server for most of our clients' websites Apache HTTP Server

We use Redis for a fast and scalable solution to caching data within our API. Redis

We use it as part of CI process to check code quality, to ensure that we're not inadvertently making common mistakes and can keep the smells and scope of code changes in line and clean. Having this step here should make future support and additions much more efficient and easy to understand. Code Climate

We use Sphinx as the main search indexing system on our clients' websites. It's a more powerful system than we even scratch the surface of, and allows us to index data from a variety of sources. Sphinx