Emmanuel Vasseur

This assignment took place within the structured finance domain, in the Liquidity team, on the Origination platform (8 teams, 90 people).

The Liquidity team develops applications that allow ALM managers (liquidity managers) to monitor their activities and optimize liquidity costs.

Within a team of 9 people and in relation with other teams on the platform, the activity revolves around the evolution of applications within the Liquidity scope:

- Continuously add features and value to the applications

- Provide technical assistance and expertise to the team, especially during application redesigns

- Participation in various chapters and community events, continuous improvement of the platform

Main functional projects:

- decommissioning of platform-specific repositories in favor of official repositories

- automation of laborious and risky manual edge cases during certain client drawdown requests

- addition of history in the application for mapping back-office deals with front-office deals

Batch module migration:

- transition from a legacy module deployed on a Windows VM to independent Spring Boot Batch components deployed as Kubernetes cronjobs

- reduction of cyclomatic complexity by 2 and cognitive complexity by 3

- creation of dashboards in Kibana to monitor batch execution and be proactive in case of errors

Rewriting of the 2 major frontend components:

- transition from Maven modules containing Javascript/AngularJS code exposed by backends to independent TypeScript/Angular components

- isolation of business rules and frontend-specific modeling in pure TypeScript code

Simplification of the main legacy monolith:

- implementation of a hexagonal architecture

- parallel run of legacy/new code with comparison of outputs and replay of audit traces for the safety net

Technical leader and software craftsman within 2 domains (10 teams).

Participation in the development of applications in an Agile/SCRUM context:

- analysis of needs, breakdown into epics and user stories, and estimation of development complexity

- definition and review of application architecture and design

- testing and development of features with adequate quality for a scalable and maintainable product over time

- implementation of indicators in metrology tools for production monitoring

Technical assistance and expertise to other teams.

Dissemination of craft & devops culture and practices:

- awareness of testing practices to have comfort and a safety net during refactoring and clean code sessions

- evangelization of code review and pair programming

- isolation of business code through modules (clean/hexagonal architecture) and modeling of business language elements using Domain Driven Design patterns

- reflection and implementation with teams of Git flows and continuous integration pipelines

- workshops with a team taking over an outsourced application to understand legacy code (implementation of automated tests, code refactoring)

- deployment of applications in the BNP Paribas dedicated cloud in collaboration with ops through docker images, kubernetes descriptors, and infra-as-code practices

- participation in the creation and animation of a community addressing difficulties encountered on the workstation and development environment at BNP Paribas

Within an agile plateau of 70 people, organized into 6 multidisciplinary and self-managed SCRUM teams, responsible for the order taking application for mass-market multi-service offers.

More than 50,000 orders are placed there daily, from mobile phones, physical stores, the online store, Liveboxes, and customer support.

The peculiarity of this plateau is its agile maturity. Since its creation 10 years ago, the teams (product owner, scrum master, development team) decide for themselves how the application should evolve.

The focus is particularly on quality with a culture of testing and software craftsmanship through BDD practices, pair and mob programming, clean code, and dojos.

Major functional projects completed:

- redesign of VOIP management within the application

- redesign of line management in view of the shutdown of the PSTN and the decommissioning of applications related to this technology

Implementation of functional tests using Cucumber:

- definition of a common language with studies and non-technical people

- replacement of GUI tests on VOIP management with functional tests to make them sustainable

- adoption by the plateau and emergence of numerous tests, subsequently integrated as a complement to functional documentation

- integration of studies into team sprints through the writing and verification of functional tests

Execution of workshops on DSL and Jenkins pipelines:

- leading workshops on new Jenkins 2 features and the implementation of DSL jobs and pipelines under Git

- conversion of existing jobs to DSL jobs under Git, normalization and factorization of job fragments

- creation of a pipeline integrating GUI tests, quality checks, and deployment to integration environment

Software craftsmanship culture:

- implementation and participation in communities of practice around development and tooling

- execution of dojos

- organization and execution of agile serious games (battlecodes)