Your developer team has the ability to organize themselves better, but they can't do it alone. Because you have too much to deal day to day, and therefore not the time to take to improve? You have old projects under python, with a huge technical debt (old paradigms, dead project branches but difficult to disentangle useful code, lack of decoupling between business, interfaces, storage ...)? Rémi is clearly the person who can help a small team to structure itself, he has a disconcerting ease in diving into code that he does not know, how to correct it, improve it, train teams so as not to fall back into the same traps. He looks for the solutions that best adapt to the functioning of the team. It is a real asset to have in the team, not to mention his kindness, his good humor and his ability to work 100% remote and adapting to colleagues with jet lag.
As CEO and founder of the Opquast project, I called on Rémi Huguet for almost the whole of 2020. The technical situation of the company before Rémi's mission was as follows: - a significant technical debt , - a very heavy and not very scalable legacy code, - a very invested technical team but which suffered more than it accommodated the requests for evolutions and functionalities - a complex service architecture - Insufficient scalability - Long development times - Applications that are too fragile I am not ashamed to present such a table, because I know that it is very frequent, even a little normal in the companies of the sector. That said, staying in a state of this type is not however possible if we want to develop, improve our agility, work faster, welcome more customers, ensure that the development teams are happy to work and informed of best practices and STATE OF THE ART. Having known Rémi for several years, I asked him to tackle all these topics head-on. Throughout 2020, Rémi worked with the developer teams and with the rest of the teams. He alternated between basic projects and much faster interventions. He organized workshops with developers and fundamentally changed the way the company works, its architecture, and its technological choices. For my part, I also had to make some major choices, but I think I can say that neither I nor my teams were abrupt or constrained during this period. Rémi has shown exceptional listening and adaptability, being able to move with ease from a strategic worksite to an urgent bugfixing site to supplement the team when needed. In short, Rémi is a very valuable resource, with excellent listening and adapting skills. His intervention with a team is at least useful and at least as far as Opquast is concerned, has been extremely profitable. This rave board would only be of value if it also mentioned weaknesses: I will mention two, one little tendency to abuse gifs and its backhand in table tennis.
I had the opportunity to work with Rémi for a year and under his leadership I have never progressed so much and in such a short time. With him, I had the feeling of being at the forefront of what is being done, both in the field of design and in the use of the latest technologies. He has this great quality of being sensitive to your arguments and recommendations. What is important for Rémi is the product, not the ego of the developers. I really enjoyed working with Rémi.
Convinced of the merits of functional tests and the TDD approach for many years, the helpless technical team could never pass the implementation stage for the main reason: methodology! What to test ? How to test it? Up to what level? The wall seemed insurmountable, no verification seemed possible without calling on the database and a lot of testing, constant frustration, hell. (Our app is 11 years old.) For many years as a good student and good soldier we have followed two perilous paths, that of the Merise method and the acceptance of ORM as the cornerstone of any good web project. It's reassuring, but there are limits. There are meetings that we know are important, that we sometimes hope for, and that we are blessed for having arrived. Rémi's is saving in many respects. Rémi's meeting is part of an important step, which, not content with having improved my own development practices, has greatly consolidated the quality of production and the resilience of the Opquast technical team. Rémi, endowed with an incredible benevolence, has the rare capacity to immediately understand your project, your module, your code, to draw out its weaknesses, to foresee the axes of improvement. Rémi accompanies you and takes you to review your thought patterns, invites you to ask yourself the right questions to meet the functional needs of your users. It seems obvious said like that, but the technical prism very often absorbs us. Rémi masters the technique, Django with us, the concepts, a large part of the design patterns but his professional experience allows him to always offer support and training, enlightened never dogmatic, a real happiness. I think you understood it, like a queen in a game of chess, Rémi is a quality resource to help your technical teams grow. PS: For lack of humor he prefers to communicate by gif, sometimes of several mega bytes, in short ecology is not his domain.