The last few years have been times of dramatic change in our lives. We have all been shaken by a worldwide pandemic and an ever more digitalized and globalized workplace. Amid these life-reshaping events, we have been trying
As developers, we all want to be efficient with each keystrokes. I have always found that most of my keystrokes were not optimized. From going from one directory to another, from searching occurrences of a word in files
Nowadays, most codebases (not to say every) depend on third-party code to avoid reinventing the wheel for every project. Dependencies exist in production-ready code as well as in tools that are used to prepare the final application. But
Thomas Villaren, Staff Engineer at PayFit, was recently a guest on French podcast Radio Contournement [https://radio.contournement.io/episode/71-thomas-villaren-a-la-decouverte-des-plateformes-low-code-et-leurs-origines] , [https://ifttd.io/] a podcast focusing on the no-code world. In this episode, Alex & Thomas focus
A codebase that constantly evolves can suffer from bugs that neither unit or integration tests can catch. At PayFit, we quickly invested in end-to-end tests to catch critical bugs before they reach production. As our engineering team grew
Hybrid functions have recently made their appearance in tech companies. These new positions are shaping the future of digital product development, made faster by the versatility of contributors. They bear many names. We at PayFit chose to name
In this post, I will share how PayFit made its codebase evolve through time, from a single repository of code to a set of functional repositories, maintained by different teams. Introduction In the early days of any startup,
Onboarding a new company is an exciting time. It can also be stressful, but in a positive way: Going to a new office, meeting all your colleagues and introducing yourself, learning more about what is expected of you
