As someone who probably gets a good dozen full-blown conference name badges a year, I mostly agree with his comments with the exception of a few things.
1. Badges with two attachment points do reduce flipping but they don't eliminate it. I'm sympathetic to using the back of a badge for useful info like a map of the venue or even a plastic sleeve for a schedule. So it's a tradeoff. But if you're not going to use the back for something useful, print on both sides.
2. Preferably use a lanyard if it's a "real" conference. It's often hard to pin stuff.
3. I get his comment on the QR codes but larger conferences need some way to scan people at booths and possibly breakouts (for attendee reports). NFC/RFID can work too and is sometimes used. Not clear to me one way is a big win over the other.
QR code on the back as he suggests seems a perfectly fine place for it. In fact, that makes it slightly less likely that I'm going to get irrelevant spam after the conference from someone scanning my badge when I didn't intend to permit it.
1. Badges with two attachment points do reduce flipping but they don't eliminate it. I'm sympathetic to using the back of a badge for useful info like a map of the venue or even a plastic sleeve for a schedule. So it's a tradeoff. But if you're not going to use the back for something useful, print on both sides.
2. Preferably use a lanyard if it's a "real" conference. It's often hard to pin stuff.
3. I get his comment on the QR codes but larger conferences need some way to scan people at booths and possibly breakouts (for attendee reports). NFC/RFID can work too and is sometimes used. Not clear to me one way is a big win over the other.