loading

Interview Series - Meet the Sprites: Guilhem

Category: careers

21 October 2020 1:00 PM
Meet the Sprites Guilhem

We speak to Lead Programmer, Guilhem Barloy, about life at Firesprite

In this interview series, we speak to some of the staff here to provide an insight into life at Firesprite from a variety of disciplines within the studio.

Today we chat with Lead Programmer, Guilhem!

Guilhem Barloy

What is your name and job title?
Hi everyone! My name is Guilhem Barloy and you may know me as one of the Lead Programmers here at Firesprite.

What does a typical day look like for a Lead Programmer?
Very much like most programmers: design and code new features, fix bugs while moaning at the poor quality of my predecessor's code (usually myself) and checking to see if someone else encountered the same crashes as I did. The lead part consists of more frequent meetings, usually lead coders, product owner group, interviews or assessments. I also need to check on the build machine and overall quality of the milestone build before it is sent to any partners for partner projects. When something is wrong, it usually falls on me to fix it! Finally, I help the other programmers on the team, by doing code reviews, trying to help with technical or design questions and ensuring that their estimates are as accurate as possible. I love coding!

What is your favourite thing about Firesprite?
I love the feeling of belonging to a family, the camaraderie. Also the fact that management is very approachable and made of game devs, and the variety of projects! It makes me feel safer about the future of the company.

What is the best advice for a Junior Programmer who wants to lead a team?
Delegate…avoid micromanaging and trust your colleague's skills. It's okay not to know everything and ask for help. Support and protect the people you manage and be friendly, but don’t lose objectivity. If you are unsure about being a lead but still want to evolve, then consider becoming a Principal Programmer instead, this way you can avoid having unhappy teams, because their lead really only wants to code and not manage people.