Date / Heure
Date(s) - 10/10/2019
18h30 - 22h00
Emplacement
Criteo
Catégories
Criteo Labs is excited to bring you our next Full Stack meetup in our Paris office. We have a great line-up of talks from both our Criteo R&D Engineers and our guest speakers.
⌚ Agenda :
6:30 pm : welcome
7:00 pm : talks
9:00 pm : networking
_______________________________________________________________________________________
# Maël Nison, senior software engineer at Datadog
📃 Yarn 2 – Upcoming Features & Vision?
Introduit il y a bientôt trois ans, Yarn s’est depuis lors taillé une solide place dans l’écosystème JavaScript grâce à sa mise au premier plan des problèmes de stabilité et de consistance. Il est maintenant temps de découvrir ce que Yarn 2 nous réserve, et vous dévoiler les prochaines étapes de notre plan visant à rendre vos applications plus stables, et vos cycles de développement plus abordables.
# Nicolas Ulrich, senior software engineer at Criteo
📃 State Management with Angular
Why do we want to use a state management library in the first place? The need comes from the ever-growing complexity of the Single-Page Applications (SPA) we are building. We have to handle more data, offering an intuitive and interactive experience to our users while constantly adding new features.
During this talk I will give you an overview of our journey in the Angular “State Management” eco-system: The reasons why we wanted to switch to a Redux-like state management mechanism and how did we choose a specific library.
# Erik Uzureau, Front-end Engineer at Datadog
📃 Code Review has gone mainstream, but nobody ever taught us how to do it right! As an engineer, can you change your mindset to write code optimised for easier/faster/better Code Reviews? What are some common anti-patterns and the git skills you need to fix them?
Nearly all successful software projects today are developed by teams of developers working together on a shared code base.
Code Review (in its many flavours) is one technique used more and more by professional software firms and open source projects to facilitate an effective development process.
At first, knowing that somebody else will be reading your code can be frightening; this is not something they taught us in school! But have no fear: Writing code for code review is an art and you can learn it.
Erik has spent the last 8 years of his career writing and reviewing code at companies with strict Code Review cultures. He’ll explain the mental switch we need to start writing code for code review as well as some of the most common anti-patterns and their remedies. He’ll share a few pro tips for writing exceptional pull requests, and will finish off with a quick live coding showing the two git commands you need to know to write the perfect commit.
# Thomas Peyrard, Senior Software Engineer at Criteo
📃 Automatic Generation of REST Clients
You’ve spent time to carefully design your REST API, and now you would like people to use it everywhere. Or you consume a REST API and you’re bothered to change your code every time there is an API change.
I’ll tell you how simple it is to generate REST clients in any languages, from your backend code to continuous delivery.
At Criteo, we use open source tools (Swagger, OpenAPI Generator, Github & Travis CI) to generate daily API clients in Python and Java for https://api.criteo.com.
https://www.meetup.com/fr-FR/Criteo-Labs-Tech-Talks/events/264775768/
