Week 5
Date: 16.03.2026 - 20.03.2026
Role: dev in team Tracing / extern in team robot
Activities
-
Audit of the robot pipeline
- Action: From my fresh perspective, provide a feedback on the robot pipeline ur3e-control
- Artefacts: Report file
-
Handling of small color artefacts
- Action: Handle small color artefacts (remove) to avoid tracing undrawable island
- Artefacts: PR link
-
Fill slicing debugging
Blocker & resolution
- Problem: When trying to solve the fill slicing bug, I probably lost time looking for a solution/ existing method.
- Solution: Taking a step back on the problem, corretly identifying it's nature can reveal simple tricks when the right angle of attack is found.
Self-reflection
What went well?
- I found the homeworking on wednesday to be productive. Certainly due to the lack of distraction at home.
What could be improved?
- Documentation of updates. PR informations aren't always best format to save informations.
What did you learn?
- Sometimes, a simple homemade trick is worth more than looking for specific existing solutions
Hiring questions
Q1: How do you ensure that you do not spill over onto a complex solution when debugging ?
A: I first need to clearly identified the problem, it's nature, source, effect. Then I should take in account it's gravity and time allowed to solve it. Furthermore, looking for existing solutions to similar problem is a good way to start, only if no evident/easy solution hasn't revealed itself prior.
Q2: Is switching someone team for a day a good strategy ?
A: Generally no. The productivity of the switched person won't be to "standard" level until few hours in (depend of the new environement complexity). However, as it was done with me this week, to get a fresh view and in the spite of a "small" job, taking in account that I had nothing better (pushing the team toward our general goal) to do. It can easily be called a healthy exeption to that rule.
Q3: How did you adapt changing team/working on a completely different topic for a day ?
A: I first took contact with team members to get a first overview and make sure to understand their expectations. I then continue by going through the pipeline as it would be executed, to increase my understanding. In a second pass, I took more time to understand some unclear sections, with when needed help from team members to facilitate the process. During the whole process I took note of questions and interesting points for my mission.