Just tell ‘em that!

We had an internal RFC comment/discussion meeting on a proposed engineering standard. In that exact meeting, a dev flipped out and expressed exasperation that they weren’t asked to comment on the proposal. In the exact meeting that was one in a series of opportunities to comment on the proposal…

▲

robertlagrant 2 days ago | parent | next [-]

Yes, this is pretty universal I think. Some people think software engineering in a team is writing code as much as possible, and doing anything else is bad.

▲

skywhopper 2 days ago | parent | prev [-]

Did they get to read the RFC before the meeting? If they had access but didn’t use it, then this is out of line. But if they only got the RFC during the meeting when they were asked to comment, then flipping out is overboard but the feeling is understandable.

	▲	sokoloff a day ago \| parent [-]
		Fair Q. It was a multi-week process where the doc was published/open for written comment and then we had a series of meetings for live discussion as well. The engineer in question just completely mis-read where we were in the process and thought this was being announced as a mandate in the one particular meeting.