Meet Sébastien, Mobile Developer at Atipik

What is your expertise as a mobile developer?

As a mobile developer, I have to be up to date on what is possible with the current means. But also to be able to estimate, as accurately as possible, the time needed to successfully complete new projects.

Summarize in a few words your daily life in the Atipik team!

Once settled at my desk with the first coffee of the day (the first of a long series), I launch the essential software:

• Slack, to stay available and accessible to everyone.
• Trello, to keep track of ongoing projects and tasks.
• Xcode & Android Studio, development platforms.
• Tower, the best Git client for Mac.
• As well as a whole series of other tools that are essential when you're doing mobile development.

After starting the day with a few first lines of code, it's time for the daily meeting where everyone shares what they did the day before and what they will do the same day.

The day continues between development, code review, support, technology watch, meetings, cheese fondue, puns and other spoonerisms.

What motivates or inspires you on a daily basis?

Software development is kind of like Lego, the possibilities are endless except that with computers we are not limited in the number of bricks. I think this is one of the reasons why after ten years I still enjoy building new apps, with various projects and always new pieces to assemble.

The opportunity to learn more and more in a really motivated and passionate team. It's a real pleasure to be able to share, discover and learn new technologies with the members of our team.

Alone we go faster, but together we go further.

What are your tips to become a better developer?

#1 Stay curious, learn by yourself but especially learn from others. Regular training in new technologies in our field is essential, but nothing beats the experience I have acquired in recent years from all the people I have worked with.

#2 To appreciate a job well done, not to limit oneself to the simple fact that one's code can work and achieve what it was written for. Think about its global impact through the project(s) in which it will be used, potential errors and other borderline cases.

#Always try to simplify your code, rather than going for complex solutions that will turn into real technical challenges of understanding when you come back to your code after a while. You will thank yourself by working on the same project several months or years later, and so will your colleagues who work on the same projects.

#4 Avoid taking unnecessary shortcuts, for example by wanting to add a library to your project to avoid developing a small feature. The time saved at first can lead to integration problems in the future. Always ask yourself the question, is this library really essential to your project or could you write the code yourself to meet your needs in a reasonable time?

#5 The Rubber Duck, for stubborn error resolution, I recommend the "Rubber Duck" method. This method consists in explaining aloud your problem to someone you are talking to, which very often allows you to understand your mistake yourself.

#6 Jogging, finally, when you are running in circles on a problem and its ideal solution, I also recommend the jogging method, I often get my best ideas while running.

#Bonus, never use a Storyboard for your iOS projects!

What is Atipikal about you?

Even if, as a geek, I love to be on my computer, it is on the trails, and in the mountains if possible, that I have the most fun. It's already been several years since I caught the Trail Running virus with a particular interest for "ultra distances". My last madness to date, the complete crossing of the Belledone massif, the "Échappée Belle", an incredible 149 km long adventure with 11'400 meters of positive altitude difference.

I think I can even say that I practice "ultra soft mobility" on a daily basis, indeed, even if in the past I still took public transportation, today I do all my trips between work and home by bike or running.