The kind of engineer I wanted to become was not the loudest person in the room.
I wanted to be the person whose work could be followed after the meeting ended. That means writing down design choices clearly, especially the ones that later needed rework. A one-line record with the date, the missed constraint and the person who spotted it is more useful than pretending the original plan was obvious.
Those notes are uncomfortable, but they are practical. Before reviewing a system in the same area again, I can look back at what I missed last time. Was it ownership? Cost? A dependency? A security assumption that nobody tested? The pattern matters more than the embarrassment.
I also learned not to volunteer for every architecture conversation just to look useful. If the last few notes show the same blind spot, the better move is to study that area before offering strong opinions.
Good engineering maturity is not never being wrong. It is becoming easier to correct because the work leaves a trail.