At Tines, we have two types of on-call: daytime and out-of-hours. In this blog, we explain the daytime on-call shift, its pros and cons, and how we make it easier by using Tines.

As her first year as a graduate software engineer comes to an end, Izabela shares her top five lessons learned that give an insight into life at Tines and tips for new software engineer graduates.

Every incident presents an opportunity, and here we examine why we replaced our old scheduler with something more reliable.

While other software companies are returning to offices, Tines is continuing with its contemporary approach to the workday - all engineering positions are optionally remote. Here’s what my typical day looks like.

We’re delighted to announce that we have recently begun sponsoring the excellent Lezer parser system from the codemirror team.

A frequent, valid objection to the concept of a "full-stack" engineer is that there is just too much to know.

Things have been changing on the engineering team at Tines. With the team continuing to grow in size, we’re getting to the point where we have too many people to treat ourselves as one team with one manager. So, we need to introduce a new role on our team - Engineering Manager.

A while back, we encountered an odd problem. All of a sudden, building our front-end went from taking a few seconds to taking a few minutes. We felt this most acutely when starting our front-end development server.

After just over a year in the industry, I wanted to reflect on my experience and the things I learned that helped me on my continuous journey to becoming an effective Software Engineer.

A while back, we talked about the coding exercise that forms part of our hiring process and what we're looking for when reviewing submissions. If a candidate's submission is successful, the next stages of our process involve them talking to our engineering team about their experiences, and pairing with them to add features to their submission.

We sought to unify the access path for both the REST API and the Web app. We found that the best way to do this was to use the existing GraphQL API implementation to power both the Web App and the REST API. This is how we did it.

Metaphors and similes are some of the most powerful tools for thinking available to us as software engineers. They allow us to apply intuition we’ve developed in one domain to another.

Relay is a JavaScript framework for fetching and updating GraphQL data in React. This is achieved by declaring the data requirements on a per-component basis while Relay takes care of optimising data fetching and performance.

We’re all getting quite familiar with the sunk cost fallacy as it applies to building software products. Projects that run to completion when their failure is a foregone conclusion.

Even when you’re told it won’t work, always try the simple thing first. Surprisingly often, it’s enough.