When I used to deal with people straight out of school they would always talk about the OSI model and it would drive me crazy. Everything we did would have to be categorized. What layer is this in, what layer is that in. I just want you to plug that Ethernet cable into that switch port and configure the static IP address in the software so we can get the hell out of here and have a beer.
No amount of explaining that stuff in the real world doesn't neatly fit into those categories would get them to shut up about it. One guy nearly had a mental breakdown when he first came across a tunnel. "How can you have two network layers?!?"
One day I was installing something in a computer lab at a college and on the wall was a giant poster of the OSI model with all the protocols imaginable listed on it. I had to fight the urge to set it on fire...
Yes, models are great for teaching and for certain types of discussions (L2 vs L3 switches) but the real world is always more complicated and the lines in the model tend to blur. Take the basic computer model taught to new students with the CPU, memory, input, output, storage, networking all neatly connected in that familiar diagram. A real computer is never connected that way. Memory is all over the place, storage can be directly on the CPU or hundreds of feet away in another box, etc.
Students quickly figure out that the computer model is just a teaching tool. Just holding a motherboard quickly makes them see that. But for networking they seem to hang on to the OSI model like if it were a piece of flotsam after a shipwreck.