fbpx

The Software Developer Learning Curve – Teem Insights with Antoine Robillard

Teem Insights is a way for key stakeholders at Teemo to share their feedback and insights with the rest of the world. 

Becoming a Software Developer

Richard

For Teem Insights, I’m here with Antoine Robillard who is a software developer here at Teemo. Antoine, can you tell me a little bit about your career before Teemo?

 

Antoine

Hi Richard. So I actually just graduated a year ago. So this job here at Teemo is my first one. So before coming here I was an engineer student at Centrale Lille, which is an engineering school that is quite well known in France.

 

Richard

That’s very interesting. So this being your first job, can you tell me about some of the things you started doing when you first got here and about how your role has changed since then?

 

Antoine

Of course. When I first came to Teemo, I was quite an inexperienced. So I took quite a bit of time to get to know the projects and our components. I was working with my teammates to improve the quality of my work. So the biggest change between and then is that I’m starting to gain quite a bit of expertise in my role.

 

Fusing the Software Development Teams

Richard

That’s awesome. It’s great to hear that you’re gaining experience and growing your expertise. Can you tell me a little bit about the types of teams that you’re working with? I know we have a lot of developers here at Teemo. What kind of role do you play?

 

Antoine

Yes, of course. So actually that is a changing. There used to be two developer teams at Teemo. The one that I was on was the DSP team. That team is in charge of maintaining and creating new features in our bidding stack. So everything that goes from complaint management to the bidding, and everything in between. And the other developer team was the visit team, which was in charge of a recording visits and sending that feature to our clients. And nowadays the two teams are fused. So I can say, simply, I’m on the developer team.

 

Richard

That’s awesome. With those teams coming together, what sort of value does that create for us?

 

Antoine

Well, it allows every developer to be better acquainted with everything that’s in our technical stack. For example, I didn’t know about the projects the visit team was working on and vice-versa. So while it’s a bit of a challenge to manage so many projects, it is also more interesting and creates better communication and alignment.

 

Richard

Yeah, that makes sense. So you’re a software developer, you’re in the back end all day. Us sales, marketing, and account people are on the front lines. What would you want us to know?

 

Antoine

I think the thing that would be hard to understand when you’re not on the back end is the fact that we’re doing as much maintenance and building as we can. But sometimes we have to take a bit of time to do what we call technical features. These features don’t really bring any new functionality to the business. But they allow for code that stays clean and an architecture that is easily understandable. So while we may lose some time in the short term working on those features, they have a lot of long term benefits in increasing efficiency and eliminating legacy code. And it enables developers to continue to deliver fast down the road.

 

Clean Coding

Anytime we do work, we take the approach of leaving the place cleaner than we found it.

Richard

Okay. Gotcha. So you spoke a little bit about making technical changes that keep everything fresh and up to date and limiting legacy code. How do we keep our software bug free and up to date in general?

 

Antoine

Well having a software that is completely bug free is almost impossible. But we’re doing a lot of things to avoid issues. We do internal reviews. So anytime someone makes a change, the rest of the team checks it. And this allows for a first check. And after that, of course, there may be bugs that still happen. So we are using tools to monitor as many metrics as possible in our system. That way, we can react as fast as possible when we see something that is wrong.

Anytime we do work, we take the approach of leaving the place cleaner than we found it. So when we’re doing a feature we might see a bit of code that is weird. And if we think it’s a change we can easily make, we do it. And we do it even if it has nothing to do with what we are developing. And so the code is always evolving and we try to make it better every day.

 

Richard

That makes sense. I liked the way you put it up, leaving things cleaner than, than you found them. So what do you thinks next for Teemo and the software development team? Are there any exciting concepts that you’re working on or anything that you’d like to bring to reality?

 

Antoine

Right now we’re working on a, a few really interesting features. These will make the job of the operations guys a little easier and automate a good chunk of their work. Some of our components won’t have much noticeable impact for front end people, but it will be make our product a lot more performant and easy to use later.

 

Richard

So for the long term, it’s gonna make things easier for you guys, which will ultimately make things easier.

 

Antoine

Correct.

 

Richard

That’s great. Well, that’s when I really want to thank you for joining me today.

 

Antoine

Thank you for coming to talk to everyone and for making our job well known to everyone.

Antoine Robillard Software Developer

Antoine Robillard is a Software Developer at Teemo who recently graduated. You can connect with Antoine on LinkedIn.