I'm a self-taught web backend software engineer, with 5 years of professional experience, from the east of France. I work primarily with modern PHP and MySQL, as the main backend engineer and Production Manager at Freshmile, building and maintaining our internal applications, based on the Laravel framework.
See my resume for more informations on past experiences.
Despite working mostly with PHP/MySQL until now, I'm open and curious about other backend technologies, particularly Go and PostgreSQL.
I’m product-minded and customer-oriented. I understand that my team's goal is to create value for customers mostly by delivering well crafted and useful features to a software product.
I favor "boring", tries-and-tested technologies over shiny new toys. But I'm always on the lookout and ready to try interesting new stuffs, to understand how they could improve the customer or developer experience.
I’m not afraid of Legacy. I understand where it come from and that most often it is the thing that provide the most value and pays the bills (and salaries).
I like working in a product-led company where things are built to last. Better yet if the customers we will interact with are coworkers from the company's other departments.
I can dabble in JavaScript but can't do that much more than edits to pre-existing Vue.js components.
I'm not particularly interested in the front-end aspect of web dev but is instead much more open in the backend : performance, security, observability, databases, refactorings, etc...
Regarding code and PHP specifically, working extensively with Laravel for over 4 years, several versions of if and PHP itself made me appreciate simple, straightforward, strongly typed and statically analysable code (so basically what Laravel isn't :/).
Today I strive to create simpler applications, where the framework would be reduced to a minimum, instead of something you are supposed to "embrace" and follow the doctrine of even in your business/domain layer.
I believe that third party code (other dependencies) should be taken into account when talking about the complexity of the app and should as such be considered very carefully before adding one.
Dependencies should then also be reduced to a minimum and that it's in many case more pertinent in the long term to reimplement (but not reinvent) simpler features in your projects so that it exactly match your needs and quality level.
Embracing PHP's type system and third party static analysers to create "strongly" typed applications (at least as much as PHP allows) is one of the best way today (along with tests) to build resilient and easier to maintain applications.
You can explore this website to learn more about the learning resources I create and the web projects I work on.
You can also checkout some of the code I wrote in the past on my Github account.