Tech Standards: Superagent

At Tes, we use superagent as our standard request library.

Three years ago, a review of our codebase showed that we had six different request libraries in use on the client side across our different services: superagent, isomorphic-fetch, browser-request, whatwg-fetch, reqwest, and axios.

Engineers had a discussion to try to find a single library to meet all our needs.


The Art of Pull Requests

I joined TES 3 months ago and in that time have been reflecting on some things I have learnt - raising good PRs is one of them. My prior experience is using trunk based development, where everyone on the team commits to the master branch. I work in the Security Engineering team now and we use PRs a lot, which was new for me. One of our responsibilities in the team is to look after the AAA services.


Contributing to Open Source is easier than you think

At Tes we have a weekly knowledge sharing session. As part of this, Rouan recently shared some tips for how to get started with contributing to open source projects. Turns out, it’s easier than you might have thought. Even better, you can probably do it as part of your daily work! In his presentation Rouan also explores reasons for contributing to open source and gives examples for how he got started.


Exceptional Alerts - Instrumenting and Observing Part 3

Observing what happens when your users interact with your software keep you from disaster, allowing your users to keep working and you to keep shipping. At Tes we capture what happens when our users interact with our services. We set expectations on outcomes. This means we know when our users can’t reach their goals. It also means we can act fast to fix problems. In this blog post I’ll show how alerts help with this and how we make this a team-focused activity.


J on the Beach - A Review

This May I was lucky enough to attend the J on the Beach conference, in Marbella, Spain. The event is able to (just about truthfully) advertise itself as ‘on the beach’, but given the proliferation of ‘data’ and ‘DevOps’ conferences, did it stand out? Did it succeed in its aim of unifying us all around Big Data? And, most importantly, what does the ‘J’ stand for?


Enabling a secure culture in engineering: the SecEng Team

A sense of separation has sometimes existed between Security and Development, as though the two are not inherently connected. Security considerations have always fed into the way we work at Tes, but without the right connections it can be easy to end up viewing security as an impediment to speedy delivery or vice versa. We started a Security Engineering team (‘SecEng’ if you like) to bridge this gap and ensure our engineering teams see strong security in data handling as critical, and crucially, something firmly within reach.