Testimonies ⭐


An absolute genius of a developer and someone I would recommend instantly to anyone. He was up to speed and operational on our processes and platforms in double time. He is well versed in architectural patterns like clean architecture and he was contributing from day 1. Exactly what you want from a freelance developer - a lovely person and absolute team player, seeking out his colleagues in order to deliver with quality and speed. A must hire if you get the chance

Nitsan Seniak

CTO - MEE6

I had the chance to work with RĂ©mi for over a year and a half. RĂ©mi joined a project that already had a long history, and he was able to very quickly enter a large code base and immediately have an impact. RĂ©mi impressed me with his ability to tackle complex business issues in an incremental and pragmatic way and to produce high quality and very maintainable code and architecture. RĂ©mi also quickly gained influence among team members - including the most experienced ones, myself included - thanks to his great culture in methodology and architecture. With teaching and patience, he made us grow by helping us adopt better practices, such as clean architecture. RĂ©mi has had a positive impact well beyond his direct contribution to the code. I highly recommend it.

I had the pleasure of working with RĂ©mi during his mission at Backmarket. Upon my arrival, he was always available to help me adapt to my role as the team manager. RĂ©mi is both pedagogical and dedicated. He consistently shares his insights constructively, and his experience enables him to understand topics thoroughly and make relevant contributions. I recommend RĂ©mi 100%.

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.

RĂ©mi is an outstanding developer with whom I had the chance to work! The quality of his work is remarkable, reflecting his rigor and attention to detail. His critical thinking was able to provide innovative solutions to the problems encountered (whether purely tech or product): in summary, RĂ©mi was a key element of the team, whom I therefore highly recommend :)

RĂ©mi is one of the most experienced developers I've worked with. I was impressed by how quickly RĂ©mi became the technical pillar of our team. RĂ©mi is very independent and has a real ability to solve complex technical problems thanks to his expertise, particularly in Python. RĂ©mi was also very valuable to our team from a human point of view. Always available and a teacher, RĂ©mi naturally took on the role of technical referent within the team. Finally, RĂ©mi went further than his role as a developer by participating in technical discussions at the group sender level and by being a force to proposal to improve our working methods. I can only recommend RĂ©mi because working with him is efficient and pleasant. I hope to have the opportunity to collaborate with him again in the future!

RĂ©mi is a very good backend developer who consistently delivers outstanding features with meticulous attention to detail. He also excels as a teacher, serving as an invaluable source of inspiration for best coding practices such as TDD and clean architecture. Without reservation, I endorse RĂ©mi and his contributions !

RĂ©mi has been a total pleasure to work with from a Product/Support perspective, being a great example of what it is like to collaborate with an experienced senior software developer. Whatever needs or questions I had, RĂ©mi was there to address them fully, not missing anything, resolving not only the request itself, but reasons for it as well, and finally making adjustments, plans or notes for the future. Additionally, RĂ©mi well documented the system that was developed, which served us well as a reference point. I would be happy and confident to work with RĂ©mi on any project or product.

Mickaël Hoareau

Software engineer - Opquast

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.

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.

Camille Wintz

Dev front - MEE6

RĂ©mi is an excellent developer and a very good architect. Within our team, he was able to set up processes and support developers throughout the change. Very reliable and friendly, he is always ready to help when needed.

RĂ©mi has been a great help to our developer team. It allowed us to avoid many pitfalls, to make ourselves aware of good practices and to get a foothold in TDD. As a junior developer, his expertise has only been more valuable. Thanks to him, our project will be able to grow on a healthy basis.

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.