Max Blassin

By joining the Source team, my mission was to set up the Source design system library. This has become the main mandatory solution for Enedis web projects. This library was multi-technology (Angular and React), so I had to set up a sustainable solution to move forward in parallel on these two technologies.

The context was complex and required me to be versatile and proactive. I was also led to set up:

- the monorepo architecture with a common file system between Angular and React,

- the library build procedure (Angular + React), importing its common files and style sheets,

- CI/CD on GitHub to put this library into production and distribute it via an internal npm repository,

- the interactive Storybook documentation of the library,

- the robust automated testing strategy to ensure impeccable quality of the components produced,

- the versioning and compatibility strategy of the library and the Angular version updates,

- the manual testing strategy of "consumer" situation to ensure that the library installs and exports its elements well.

In addition to these missions, I was led to:

- onboard new projects, manage bug reports, feature requests from the community,

- validate and edit community contributions,

- regularly present new components and bug fixes during monthly demos addressed to consumers.

Each decision was the result of productive discussions, and we were keen to ensure that our components were excellent, flexible, accessible according to RGAA criteria, and corresponded to the designers' requests to the pixel.

In the end, more than 40 components were produced during this mission and a total of more than 100 projects for about 30 teams had adopted Source at the end of my mission.

Mission as a Front-End expert on Angular.

In this mission, I had the opportunity to work on Professional and Patient portals in the medical field. These portals are then used in clinics and hospitals to allow healthcare professionals to manage patient records and patients to access their documents, appointments or invoices.

This mission had several main axes:

As a Front-End developer, I was accompanied by a substantial and changing team in Agile methodology. I had the opportunity to work in a team with other front-end developers. I was led, among other things, to implement features such as deep links, the payment system, or the history of professional access to patient records. I was also led to enrich the company's internal component library. I also contributed to the resolution of anomalies, including some criticisms in terms of time following releases.

The challenge of this mission was a quick understanding of the existing which was massive, and an improvement of it with sometimes missing documentation which allowed me to be proactive and inventive in my solutions. I also had the pleasure of exchanging, and my improvement approach was always proposal and discussions, in the idea of a common construction.

The technologies that I was led to use were Angular, Storybook, Git, Gitea, Docker and Figma.

Mission as a developer on Angular 13.

In the context of this mission, I developed new features for the payment management part of the Agicap product which allows its customers, companies, to manage their expenses.

I joined an Agile squad divided into several teams. Within my team, I had the pleasure of working in an international context, in English, with very sharp profiles both on front-end and back-end technologies.

I therefore realized in Angular 13, with Nx and NgRx, new features such as modifications of payment information, the management of beneficiaries, or the reconciliation of accounting data.

I also had the pleasure of setting up acceptance tests via Playwright as well as end to end (E2E) tests. We also did unit tests with Jest.

We worked in CI/CD on a Docker and Kubernetes stack with Gitlab-CI, and I had the opportunity to discuss these topics and work on these topics with competent DevOps in a skills development approach.

In this mission, we valued the DDD (Domain Driven Design) approach, which was central to our developments and interactions with Design and Product. I was led to think a lot about the structure of the code, its division, its tree structure and the dependencies of the modules I created, and I was thus able to improve myself in these areas. We discussed these topics very frequently, and I had the pleasure in particular of initiating the launch of a product from scratch using this DDD approach, which earned me a lot of reflection, challenge, and progressive and strategic implementation of code (continuous deployment, feature flags...).

This experience allowed me to touch on very specific topics that strengthened my ability to prioritize my code and intelligently launch new features.