I first met Fabien 3 years ago, only through his code. I had to maintain the code he had written before leaving. It was an easy task as far as his code was clean and no bug were found. It was the only time in my carreer I enjoyed maintaining someone else's code. I currently have the pleasure to work with him. I've finally discovered the guy behind the code I had to maintain. Fabien is currently in charge of developing an Angular-based framework for the OPW, and all I can say is that the job is really well done! In addition to that, Fabien shares the knowledge he has acquired actively.

Fabien is the kind of guy that will simply tell you that "it's done"... when you asked him to have a look at something that didn't work so well. It's done? ... it means, it's DONE, I mean really done, totally solved, fixed, all the issues are solved and more! Now there is unit tests, he founds another bug and solved it, rewrote your class to clarify the code, added documentation, fixed your error (the one you didn't test), pointed out some potential issues, added logging, fail-over mechanism, reduced the load, corrected your XML, commited the changes and finally send a mail with a simple sentence: "it's done". I really enjoyed working with you. I learned a lot... thank you.

I first met Fabien 3 years ago, only through his code. I had to maintain the code he had written before leaving. It was an easy task as far as his code was clean and no bug were found. It was the only time in my carreer I enjoyed maintaining someone else's code. I currently have the pleasure to work with him. I've finally discovered the guy behind the code I had to maintain. Fabien is currently in charge of developing an Angular-based framework for the OPW, and all I can say is that the job is really well done! In addition to that, Fabien shares the knowledge he has acquired actively.

Fabien is the kind of guy that will simply tell you that "it's done"... when you asked him to have a look at something that didn't work so well. It's done? ... it means, it's DONE, I mean really done, totally solved, fixed, all the issues are solved and more! Now there is unit tests, he founds another bug and solved it, rewrote your class to clarify the code, added documentation, fixed your error (the one you didn't test), pointed out some potential issues, added logging, fail-over mechanism, reduced the load, corrected your XML, commited the changes and finally send a mail with a simple sentence: "it's done". I really enjoyed working with you. I learned a lot... thank you.

I first met Fabien 3 years ago, only through his code. I had to maintain the code he had written before leaving. It was an easy task as far as his code was clean and no bug were found. It was the only time in my carreer I enjoyed maintaining someone else's code. I currently have the pleasure to work with him. I've finally discovered the guy behind the code I had to maintain. Fabien is currently in charge of developing an Angular-based framework for the OPW, and all I can say is that the job is really well done! In addition to that, Fabien shares the knowledge he has acquired actively.

Fabien is the kind of guy that will simply tell you that "it's done"... when you asked him to have a look at something that didn't work so well. It's done? ... it means, it's DONE, I mean really done, totally solved, fixed, all the issues are solved and more! Now there is unit tests, he founds another bug and solved it, rewrote your class to clarify the code, added documentation, fixed your error (the one you didn't test), pointed out some potential issues, added logging, fail-over mechanism, reduced the load, corrected your XML, commited the changes and finally send a mail with a simple sentence: "it's done". I really enjoyed working with you. I learned a lot... thank you.