This might not be quite what the previous poster meant, but in my experience it's often not that the developer missed a meeting and now doesn't know some critical piece of information. Rather, it's often that the developer has some knowledge about the code that changes how something should be implemented. Because they weren't at the meeting, nobody else knew about this, and it's only later, when the developer sits down to write the code, that everyone finds out.

In this case, there's nothing to document from the meeting because the information wasn't shared in the first place. The information could only have been shared if the developer had been in the meeting.

(FWIW, I've rarely seen this from a developer not being in a meeting entirely, but I've seen it a few times where a developer has treated the meeting as a "read-only" event, i.e. expected that other people provide all the requirements and not used their own expertise or experience of the code to push back on decisions.)

▲

coliveira 2 days ago | parent [-]

The point in the parent comment still stands. There should be a paper trail so that the developer would have to confront the need to add such a detail. If the decision was made in the meeting alone, then it was lost in time as not all developers can be expected to be in every meeting.

	▲	scott_w a day ago \| parent \| next [-]
		How? Meeting notes can never contain all the detail of the meeting and, if they do, there would be so much content that you'd likely miss them when you read the documentation. That's to say nothing of the time investment of the person to catch up on every document produced. In that case, you're essentially relying on the people in the meeting to know they should document that thing as important which, given the person who knows it's important isn't there, is pretty unlikely. Even in an ideal world, we'll have developers not in the meetings they need to be in. My contention would be that we should try to get people in the right meetings and, over time, the number of issues where someone isn't in the right meeting will be lower than if we just don't have those meetings.
	▲	MrJohz a day ago \| parent \| prev [-]
		If decisions are being made about the code or implementation, then the person working on that code should be in that meeting, surely. Otherwise there's no point making that decision.