Re: What...no bitwise shift operators
who knew that Ethernet uses "Collection Detection".
"Knowledge of Carrier Sense Multiple Access/
Collection Detection (CSMA/CD) as used in,
for example, Ethernet, is not required"
184.108.40.206 Data Compression
They don't even talk about discrete cosine transformation compression like used in JPEG?
220.127.116.11 Logic Gates
Better add in the quantum devices they're coming up with!
18.104.22.168 Internet security
"Discuss worms, trojans and viruses, and the
vulnerabilities that they exploit." wow...all of them? In one unit?
22.214.171.124 Client Server Model
Compare JSON with XML...which they never introduced. They never even introduced "markup" languages at all; even as a class of language.
Wow..that is one horribly out of date unit. None of the modern DB architectures are there.
126.96.36.199 Functional Language Programs
Includes a list of function languages that the student can use, except that only one (Haskel) is in the list of supported languages way at the top. How would they teach functional programming in a language they don't actually know or use?
"Know the criteria for evaluating a computer system"
They're kidding, right? The criteria could include any aspect of the hardware, software, and systems that is a measurable characteristic.
188.8.131.52.2 Techniques use (for the project)
So, now come so much emphasis in the grade is on "excellent coding style characteristic", although from everything I read, there is NO actual teaching about coding style. A search shows that "coding style" only shows up in testing. They certainly go into in depth as to how a student should use in 184.108.40.206.2, but they don't seem to ever actually present that to students. Osmosis maybe? Beware, kiddies, neatness counts!
Okay, same kind of thing, 220.127.116.11.2, Coding styles
They claim excellent programming uses "Defensive Programming", and yet NONE of that was touched on in the course materials. That is NOT a topic to simply leave out.
Overall, there seems to be a dearth of teaching about how to actually decompose a real design, and evaluate it critically against many different criteria. That's not always a straightforward thing, and optimization work techniques like refactoring should be part of any programmer's understanding.
Okay, that's it...I'm not reviewing the teacher logistical hoo-hah.
Do I pass?