Skip to content

Week 3

Date: 02.03.2026 - 06.03.2026

Role: dev in team Tracing

Activities

  • Tracing pipeline implementation

    • Action: Implements an update of the detect_islands() function and the needed part of the Tracer class to enable multi-layer borders detection
    • Artefacts: PR link)
    • Justification: This function extension requiered understanding of the pipeline and was designed with modularity in mind (Class Hierarchy new methods).
    • Skill related: Applying computer engineering skills to the field of data

  • Meeting report

    • Action: Take the minutes of a daily meeting
    • Artefacts: Daily meeting report file (PDF form)
    • Justification: Applying summarizing skill and be able to summarize content
    • Skill related: communicate clearly and effectively

Blocker & resolution

  • Problem: The meeting with the client was still no professional enough. We didn't bring enough pertinent datas, to allow the client to take the expected decision.

  • Solution: We need to provide the client with quality informations, to allow him to take any decision with confidence.

  • Problem: Some workforce task distribution led to double work done

  • Solution: Clarity in the teams and a check from the chief are sometimes needed to ensure that the general direction to success is still followed.

Self-reflection

What went well?

  • The track toward project success is maintened (but need to be overwatched)

What could be improved?

  • Our preparation of the CTO/client's meeting. The right information to valuate our work and bring deciding informations are still missing.
  • Atmospher in the working room sometimes is unproductive. Isolation and focus should be more used.
  • A better speed of execution of tasks from my part. I could improve the relative implementation speed for example.

What did you learn?

  • Sometimes decision has to be made to further advance. In such case, if a team is unabeld to do it, a superior has to take it, based on the best evidences available.
  • There is no shame in asking for help.
  • In a team, a single failure is a team failure.

Hiring questions

Q1: In your team, some members are having difficulties doing their tasks, how do you react ?

A: If I have the working time availability, I will discuss with them to propose my help. If not, I should inform my superior so that if needed the hierarchy knows the situation and can take action.

Q2: Why should you as much as possible have no hardcoded value in a pipeline (like the Tracer) ?

A: As we did in the Tracer pipeline, having all the parameters values in a config file allow to generalise across cases without direct code change.

Q3: As a developer, what concrete practices can you adopt to improve your implementation speed without deteriorating code quality?

A: I should break down the task into small, clearly scoped steps before writing any code. THis will ensure that I stay on track of the task and will reduces errors and unusefuls changes.