Yeah, for me at least. I feel like that would make a meeting more awkward, not less. Also, if I were in the new hire's shoes, scheduling a meeting that's essent

Yeah, for me at least. I feel like that would make a meeting more awkward, not less. Also, if I were in the new hire's shoes, scheduling a meeting that's essentially about criticism would make me more anxious, not less. And the time gap between the scheduling of the meeting and the start of the meeting might be pretty fretful. If someone just lays out what they want changed in 1 or 2 sentences, I can immediately know that it's not some big problem they want to meet about. At the same time, I would feel bad if I found out that I had really distressed a new hire in a code review. And I do try to soften things when I say something that I anticipate might be perceived as harsh in a way that I don't intend. (I use emoji a lot, I DM people, and I tend not to use standalone sentences that end in periods except in email. I use parentheticals and qualifiers, make jokes, etc.) I do schedule meetings to go over things including criticisms/problems/objections, but only when I feel like it would be faster and more natural, or I think it's really essential that I make a realtime demand on someone's attention to get their input.