26 Aug 2016

Progressive Web App Dev Summit – Feedback

What is it ?

The 20 and 21 of June, I had the chance to attend the Progressive Web App (PWA) Dev Summit in Amsterdam. Formerly known as the Chrome Dev Summit, this event was (very well) organized by Google, but was not a Google products event as all browser vendors were present to give a talk (engineers from Mozilla Firefox, Microsoft Edge, Samsung Internet browser and Opera, the only vendor missing was Apple Safari…).

Lire la suite …

31 Mar 2016

Setting Oracle Managed Driver Parameters

When Microsoft released .NET4, “System.Data.OracleClient” was deprecated. When you upgrade .NET framework, you’ll probably remove the references to “​System.Data.OracleClient” and reference Oracle Managed Driver instead. On one of my project, I had to face an issue caused by a difference when calling a stored procedure in passing parameters between the Microsoft and Oracle provider.

Lire la suite …

30 Mar 2016

Coding challenge: improve your delivery process!

At job, we like to develop our Software Craftsmanship culture by organizing Dojos, Katas but also, time to time, coding challenges.

So, last month, for two hours, about thirty developers were pair-programming to solve the Extreme Carpaccio problem.

I decided to ask Gilles, one of our Delivery Managers, his feedback about this event. As he is an “aficionado” of Software Craftsmanship, I think it’s interesting to share that feedback with you.

Lire la suite …

25 Mar 2016

AXA WebCenter’s Open Space Session about software craftsmanship

How to continuously improve together


Last year, the WebCenter teams were coached by Octo about software craftsmanship especially around five practices : TDD, Code Review, BDD, Clean Code And refactoring legacy code.


During this period, we received trainings, intensive coaching, we tried a lot of things to find our own way  of using these practices and participated to some events (AXA Testing Days, Agile Tour Lille 2015).

To look how far we have came with that, we organized an Open Space Session last week for every person interested in this subject at the WebCenter.


The purpose of the day was to make a retrospective about last year and to find how can we go further without coaching to keep practising and continuously improve by ourselves. There were approximately a hundred persons participating including managers, developers, QA, etc.


Schedule of the day


The day was organized in two main parts :


The first was about doing our retrospective. We were divided into three groups and each group was composed of several small teams to figure out about these themes :

  • What we’ve done
  • What we liked
  • What we’ve learned
  • What we want to start
  • What we want to keep
  • What we want to drop

We were switching teams for every subject in order to exchange with different people.
The second part was the open space session for the perspectives of 2016. People proposed many differents subjects they want to treat this year and everybody was free to join their favorites meeting to contribute to the talk.

Here is a picture of the proposed subjects :

Open space subjects

And some about the sessions :

open space  open space                                                                                     open space


What came out of the sessions


At the end of the open space, we sticked the posters up on the walls of the meeting room so that everyone could see what the others talked about.

The next steps was the moment for us to choose the most interesting subjects we want to deal with this year.

This is the ideas that were promoted after the vote :

  • Immersion with others teams to spread the knowledge
  • Meet our end users in order to have a better view from the field
  • Share our practices outside the Webcenter
  • How to improve the code review workflow/process
  • Measure our quality KPI
  • Raise awareness of TDD and BDD among the product owners




A lot of ground was covered last year but there is still a lot of work to do to keep improving about craftsmanship. It was interesting to work out together what the people from the WebCenter wanted to do during this year to take it to the next level.

La conclusion



23 Mar 2016


Why XDomain ?

Cross-Site request (request for resources located on a different domain than the source of the request) initiated by a JavaScript are restricted for security reason. The W3C has produced a recommendation for the Cross-Site Resource Sharing (CORS), this specification uses XMLHttpRequest for the API Request and supply to the web server an access for the cross-site and so provide a security transfer.

IE8 and IE9 does not support the XMLHttpRequest cross-site, Jaime Pillora has developed a solution called XDomain which work like a Javascript proxy for the API Request. The limit to this solution is that you needed access to the API to use (or it use already XDomain) and on the JavaScript application. An other solution is use directly XDomainRequest available on IE8 and IE9, the advantage to use XDomain is than you do not have to manage in your code call in XMLHttpRequest and XDomainRequest.

Lire la suite …