Comment by Davidbrcz

- Take notes of past decision (what context, deadline, available skills on the team, compromises that had to be made...).

- MR/MR contains a ref to the ticket, an explanation of the changes, proof of work or way to test the change.

- Know how to leverage your tools (git, editor)

- Be curious [other languages, tools (formal methods, fuzzing..), fields (web if you embedded, or the other way around), maths ... ]