Hacker News Reader

- 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 ... ]

Proof of work is so interesting! For backend changes, does that mean curl commands? some screenshots?

Could you give me an example format of your notes? I would love to see the detail one can get from them?

- curls commands, unit tests, screenshot ... It depend on what you work on and need to do.

- You can look up architecture decision record (ADR). There are plenty of good resources on google.