Tes engineering blog

George Maddocks was in our Security Engineering team for 6 months.

In a short video, he tells us about his role in the team and what he learnt.

The Security Engineering team does not exist to check people’s work or to instruct. Instead we are there to engage with our teams of engineers. Bringing information, useful data and tools to support engineering teams in making the right choices for their products.

Come meet STAN, a guide that plays a big part in this.

Monitoring lets our teams know when something unexpected is happening in our live environment. Our monitors keep watch, so we don’t have to.

However, systems change and so do teams. Information is forgotten, products and services may be handed over to new teams.

The biggest concerns of a year ago may be yesterday’s news. How should we keep our watchmen relevant?

Things I’ve learnt since becoming a Principal Engineer

At Tes, a Principal Engineer looks after one or more teams of engineers with the aim of helping the individuals grow and to enable the team to work together to develop and support our services. Principal Engineers across Tes Engineering meet every week and are “responsible for the overall health of the engineering team”. Read more about our management model here.

Phil, a Senior Engineer at Tes, gave a great introduction to AWS Lambdas during our weekly knowledge sharing session. These hour long sessions are meant for Tes Engineers only, but this session contained a lot of useful information that I’m sure is relevant for people outside of Tes as well.

Mentoring is essential to how we work at Tes engineering. Let’s take a look at at the value of mentoring and ways you can structure a mentor chat.

A mentor offers help in these key areas:

👂 Be a person to speak to and listen
👐 Offer support and comfort in times of stress
🧭 Help people navigate the organisation
🏋🏻‍ Help people grow capability
🎆 Celebrate success!

The future of JavaScript, delicious buttery croissants and cold, freezing Paris in December.

dotJS is part of dotConferences, an impressive series of tech conferences with the goal of bringing TED-like quality to the tech world.

Everyone who works with data worries about accidental deletion and should have a good understanding of recovery strategies, ideally before an incident occurs. If you’re using Mongo, you can restore data to an arbitrary point in time using the oplog, provided you are using replication and have a recent backup.

This blog post will walk you through a simple data deletion and recovery scenario using this method, and should be accessible even if you have limited experience with Mongo.

Back in September 2019 we decided to host a Global Day of Coderetreat event. Since we’re a remote first digital education company, this event would also be conducted remotely. The event would be globally available and would include people inside and outside of TES. A few questions you may have 🤷🏽‍♀️ What is a Coderetreat? Originated at the Codemash Conference in January 2009 by Gary Bernhardt, Patrick Welsh, Nayan Hajratwala and Corey Haines.