Cancelled
Deadline for registration: 15 days before the starting date of each training
Duration : 4 days (28 hours)

Before signing up, you may wish to report us any particular constraints  (schedules, health, unavailability…)  at the following e-mail address : training@cerfacs.fr

Abstract

This training course enables the participants to reinforce their practical knowledge in coding. Usability, maintenance, testing, reviewing are the main subjects tackled. Hands-on sessions with in-house tools are organized to put the theoretical courses into practice.

Objective of the training

First hand experience on how the code we write is used, understood, maintained and recycled – or discarded-.

Learning outcomes

The participants should be able to :

Identify some code bloatings (primitive obsession, god-class, spaghetti).
Research and select an external package adapted to his needs.
Target participants
This training session is for students, engineers, physicists and computer scientists who wish to improve their coding skills and reduce time lost in the side effects of brute force coding.

Prerequisites and registration

In order to follow this course, you need to:

• Knowledge of Unix commands.
• Basic knowledge of Python
• The training can take place in French or English depending on the audience, level B2 of the CEFR is required.

To verify that the prerequisites are satisfied, the following questionnaires must be completed. You need to get at least 75% of correct answers in order to be authorized to follow this training session. If you don’t succeed it, your subscription will not be validated. You only have two chances to complete them.

Questionnaire 1 : https://forms.gle/FjANa2aBmjAkdXH77

Questionnaire 2 : https://forms.gle/hdrT2myBB77qN7Pc8

After completing the pre-requisite test and obtaining at least 75% correct answers, you can register:

Pre-registration

Referent teacher: Antoine Dauptain

Program

Every day from 9h to 17h30

Day 1

Code review on actual code brought by the students.
Introduction to linting

Day 2

Code review on actual code brought by the students.
Introduction to code bloaters

Day 3

Code review on actual code brought by the students.
Introduction to co-development techniques

Day 4

Code review on actual code brought by the students.
Introduction to maintenance costs and testing

Pre-registration