Jay Honeck wrote:

Which led me to question why I ever read the code back in the first place?
Since the controller can obviously see the code on his screen, he certainly
knows that I have complied with his instructions.

So why do we read it back?

Because, if you don't, the controller has to hold the frequency open for the
response he's expecting, until enough time elapses that he decides you're not
going to respond, so it takes up just as much air time either way?

I dunno, I've done it both ways, and both ways seem to work, and I've never had
a complaint either way.

Normally, I do the readback, though.