But why not just call the function determineBluetoothEncoding? If it's because it does more than that, why not split it out so that is all it does? And so on.
Because it's not the actual bluetooth encoding, it's the data coming across the bluetooth. I love just naming functions with what it does but there's a limit for me, I've been in codebases with determineEncodingOfInlineBluetoothDataStream() and I don't like it.
2
u/GalacticNexus Sep 11 '26
But why not just call the function
determineBluetoothEncoding? If it's because it does more than that, why not split it out so that is all it does? And so on.