some C doesnt mean "know C"

do you know how the memory allocation works when you create a list in python by inferring from how you'd do it in C?

its a very basic question and I don't know many python devs that know the answer right off the bat. its going to be "u malloc stuff right?"

Another basic question: what happens exactly when you open and start reading a file? "u call open right?"

thats not enough to figure out how things work. Coding "real" C (as in being able to do anything in C, not just code snippets) means that you probably understand how most things work under the hood, including libc, the kernel(s), file system, etc - at a pretty good level of detail.

If you know many like that, its great, but if you think the majority (or even a third) know these things - then I also think that either you or I live in an imaginary world =p