Back in my high school days, when I started my first step towards programming for real as opposed to the stuff I've done with DOS batch files, one of the first books I read was the Camel book (Programming Perl - that's what everybody was using for their CGI scripts back then).
Their use of foo, bar and foobar without explanation was extremely confusing to me and made the whole book very difficult to understand for me as my brain constantly wasted brain cycles on trying to understand these words in the code samples.
Of course it didn't help that back then my English was practically not existent yet.
It's funny how these completely made-up words have become real jargon one has to know when working in this industry, to the point where at least for me personally, not knowing them was a huge barrier to understanding a basic book about our profession
(I might also just have been too young yet. I remember reading the chapter about regexes (littered with foobar) and thinking "nobody in their right mind can find this useful for anything")
Their use of foo, bar and foobar without explanation was extremely confusing to me and made the whole book very difficult to understand for me as my brain constantly wasted brain cycles on trying to understand these words in the code samples.
Of course it didn't help that back then my English was practically not existent yet.
It's funny how these completely made-up words have become real jargon one has to know when working in this industry, to the point where at least for me personally, not knowing them was a huge barrier to understanding a basic book about our profession
(I might also just have been too young yet. I remember reading the chapter about regexes (littered with foobar) and thinking "nobody in their right mind can find this useful for anything")