Auteur/autrice : TheCodM

Hello, my name is Sophie, I am Captain Coder for TheCodingMachine.

Two years ago, an opportunity to work at TheCodingMachine made itself available. TheCodingMachine, a tech company, was looking for a Captain Coder. 

Without having read the description, you couldn’t have imagined what kind of position it would be. Mostly requiring soft skills such as communication, curiosity, dynamism, adaptability, good english & many more skills. Intrigued, I decided to give it a chance, knowing very little about technology. David Maechler, a lead project manager at TheCodingMachine introduced me to the opportunity. He introduced me to Nicolas Peguin, one of the 4 partners of the company, we had a great connection. When he told me the story of the business model of TCM, I felt like there was something  I could offer to the company.
Graduated 11 years ago with a Master degree in Communication, I traveled around the world and experimented with different type of positions in my career. The last one was as a freelancer in Image, production & arts. I was also involved in a startup project for 2 years.

Understanding the importance and the role as a former freelancer I affiliated easily to my present position. Managing a community of freelancers, and becoming their referent echoed as getting involved into the technology world with the app project I had in the past. This is when I started digging into the concept of Open source. 

Open source put a spell on me! It’s pretty fascinating when you actually think about it as a NOOB ! A community of developers all over the world contributing to various projects … for free ! Having millions of users participating in the growth of a tool, technology, plugin, boilerplate, … Impressive! 

Back to the story of TCM and this finding, it seemed obvious. Another world to discover for me : challenge accepted! 

The link with the business model of TheCodingMachine seems pretty clear; the idea was to work with a worldwide community of contributors performing in addition to their inside team, the building of powerful & relient applications.

This is what Coders is.

The question should be, who is behind coders ?
Denis, Benjamin, Mario, Wayan, Dave, Hugo, Abigael, Mykola, Uchenna, Liginm,…

All those human beings in Coders are our community of freelancers with whom we work on our web projects everyday. 
Who are those freelancers? Where are they living ? How do we recruit them ? What’s their position at TCM? What’s their ambition for the future ?
This was my challenge. Create and federate this community.

The idea appeared to me, like an epiphany : what about empowering freelancers. What about being part of a company that values humans over the rest.Gain productivity and build up a powerful community with real humans from all over the world. Reminds you of something ? *Open source!

Finally, I accepted the challenge of taking over this ambitious project. It was already in place but with no specific process, and no one leading the project. 

I presented my vision of Coders to the board of directors. 

My main idea was to find the right match for each project, each team & each coder. As well as working on a long term relationship to make sure the teams have positive & successful experiences with each other. Through experience, make sure that their skills will grow while working with us. As well as they will bring their knowledge to the teams and projects.

Build everything from scratch and convince the collaborators that it can work. The tagline of coder became: Let’s code together! 

What are the benefits on both sides of this business model ?

• Gain productivity
• Experience growth in collaboration
• Working hours are decent for both side
• Management skills
• Multicultural experience growth
• Teaching skills
• Technology awareness
• Communication skills

Giving access to TheCodingMachine culture of work; by their choices of technologies, process of management, tools is a great opportunity for these freelancers. Coming from Ukraine, Nigeria, China, Kenya, Russia, Poland, Portugal … This worldwide community is real proof that diversity is our asset. We don’t care about where they are from, we care about their skills & their values. Working with like-minded people should not be a dream, it is a TCM reality.

How do we do it ?

• Communication : We use different types of communication tools to keep in touch with them everyday to make sure we are all in this together. My main goal everyday is to ensure we are not losing track of communication for the good of the collaboration. Creating a group of motivated people communicating better and better with their teammates. We created a dedicated map for them on workadventu.re 
• Contract : We built a platform where we have contractuals components to assign to freelancers. That is the legal guarantee they will have work and get paid. As well as confidentiality policy for every mission.
• Transparency : these values are part of the onboarding process : we prefer transparency and healthy relationships. We always pay well and on time. We actually pay every week to ensure the well financial being of the freelancers. I lead the financial part of the collaboration. 
• Mutual respect : It takes two to tango. It’s a collaboration, and like the dance if one person is not moving in the right direction, the other person cannot perform. We learn how to collaborate in an equal way.
• Group integration : as the coders are not sharing the open space like us, we need to integrate them into our routine. For example, every Friday morning we organize Tech Talks which they are all invited to. We give access to our tech blog content all written in English, as well as our technical presentations.
• Self assessment : as part of our human resources, we invite them to do a self assessment at the end of each year in order to receive and give feedback on their year and work they have completed.
• Post Mortem feedback :  after every project, we realize Post mortem to make sure we learn from our mistakes, good actions for the good of our projects. We define different aspects of the project including the collaboration with the coders.
• Invitation to Paris : the idea is to invite every year one coder or maybe in the future several, so they can come visit the office, work with us and discover Paris. The Covid-19, didn’t help to make it happen this year but hopefully soon we will be able to. Stay tuned.

This model is very ambitious and only started. We can see now a defined role emerged, Chief Freelance Officer. With this crazy year, it seemed like natural to be able to manage the relationship between your collaborators and make sure everyone is following the same direction. If you happen to be curious about the subject, please come by our office or just come talk to me s.maechler@thecodingmachine.com.
You are also welcome to visit https://workadventu.re/ come say hi and visit our different spaces.

Vous avez des problèmes de performance liés à un fort trafic ou plus globalement à votre bande passante ? Pas de panique, on vous donne quelques astuces pour réduire les flux entre votre site et le navigateur du visiteur .

3 méthodes pour mieux gérer votre bande passante

Temps de connexion, latence … Savoir poser un diagnostic pour améliorer vos temps de réponse ! 

Un navigateur Internet doit recevoir l’ensemble du code HTML (DOM) du serveur avant de pouvoir afficher le contenu. Pour chaque élément, contenu, image, vidéo etc., le navigateur se connecte au serveur grâce au protocole TCP/IP. C’est le temps de connexion.

À cela, il faut ajouter le temps de latence du serveur qui ne répondra pas toujours instantanément car il traite les demandes dans l’ordre d’arrivée. Ces temps sont irréductibles.

Maintenant, sur une page HTML classique, 70% du temps d’affichage n’est pas le temps de téléchargement, mais le temps nécessaire à la connexion auquel s’ajoute le temps de latence. La meilleure optimisation de la performance web est donc de réduire le nombre de requêtes au serveur donc réduire l’utilisation de votre bande passante. 

Il est temps maintenant de passer à la pratique et d’appliquer les bonnes méthodes !

1ère solution pour réduire votre bande passante : utiliser le cache

Les systèmes de cache évitent de recharger des éléments déjà téléchargés. Ceci permet des allers-retours serveur beaucoup plus rapides ou même de les éviter.

Par défaut, la balise HTTP Etag (entity tag) est activée, elle aide à ne pas télécharger deux fois les mêmes fichiers. Ce système n’évite pas les allers-retours client-serveur, mais de renvoyer le contenu des fichiers, et donc de trop consommer de bande passante et de limiter le traitement que doit effectuer le serveur.

Essayez https://varnish-cache.org/

2ème solution pour réduire votre bande passante : réduire le nombre de fichiers envoyés 

Plusieurs options s’offrent à vous pour réduire le nombre de fichiers, on vous en propose deux :

1. Limiter le nombre de fichier CSS et JS : Il est possible de regrouper les fichiers CSS ou JS en un seul. Plusieurs outils sont disponibles en ligne.
2. Regrouper les images – Sprite : Vous pouvez appliquer la méthode « Sprite » : il s’agit ici de regrouper les images du thème qui sont couramment utilisées en une seule. L’avantage est de n’utiliser qu’un nombre réduit d’images. En revanche, il faudra, via une feuille de style, afficher l’image en arrière-plan et la positionner.

3ème solution pour réduire votre bande passante : réduire la taille des fichiers 

Rien de sorcier, voici deux options pour réduire la taille de vos fichiers :

Réduire la taille des images
Si vous avez des images qui ne font pas partie intégrante du thème, vous devez les réduire au maximum et éviter de charger des images trop grandes. Il est préférable de les réduire ou d’utiliser des mécanismes automatiques de mise à l’échelle.

Limiter le poids des fichiers

Deux moyens sont possibles :

1. Compression Gzip : Les fichiers HTML, CSS et JavaScript sont des fichiers texte et donc particulièrement adaptés à une compression ZIP importante. Le temps nécessaire à cette décompression est négligeable pour le visiteur. En réduisant les flux envoyés aux utilisateurs, vous réaliserez une économie de bande passante.
2. Minify : Une autre possibilité pour limiter le poids de vos fichiers CSS et JavaScript est de les minimiser. La minimisation supprime les retours à la ligne, les tabulations ainsi que les commentaires. La lecture de ces fichiers devient donc quasiment impossible, mais ce n’est pas un problème en production.

Vous pouvez essayer https://www.minifier.org/

Avec toutes ces solutions, vous allez optimiser l’utilisation de votre bande passante et évidemment gagner en performance ! Les utilisateurs vont pouvoir aller plus vite sur votre site et votre SEO n’en sera que plus performant. 

Pour aller plus loin dans votre démarche, consultez notre livre blanc