I think you mean professor. Their is a difference you know!
I refuse to call him a professor until he starts acting like one. The guy is hardly a programmer. Usually when a teacher asks questions in class, it's to test the knowledge of the students. This guy asks questions because he's confused...constantly. He'll be showing us sample code (which another professor wrote for him) and he won't understand how part of it works, so he'll ask us. And then he'll stand there for 10 minutes trying to figure it out. Then he'll tell us to take a 10 minute break so he can continue to try and figure it out.Then when we get back from break, he just skips it. That happens.. constantly.
We had a lab where we had to read information from a file and output it in a specific way, and now we're re-using that code to read from a database rather than a file. He spent the entire lecture explaining to us how tables are organized in SQL... which is incredibly pointless considering that we were already given a database to use for the lab, and the tables were all already created. He did not go over how to connect to SQL at all, he did not go over how to output data from SQL.. at all. The guy is incredibly clueless when it comes to teacher, and almost as clueless when it comes to programming.