At PayFit, Product teams are divided into tribes and squads (comparable to the Spotify model). While each of them strives to be autonomous, they are backed up by the developer experience (DevXP) team. The DevXP team provides a
Meet Charles Françoise, Senior Engineer in the JetLang Platform team at PayFit! In this video, Charles answers questions about: * His background before joining PayFit, * Why he chose to join PayFit, * His preference between in-office and at-home
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
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
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
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,
Thomas Villaren, Staff Engineer at PayFit, was recently a guest on French podcast "If This Then Dev" (IFTTD [https://ifttd.io/le-dev-qui-veut-tuer-le-dev/]), hosted by Bruno Soulez. This podcast discusses trends
