Published by |
|
Senior Member
Join Date: Jul 2008
Posts: 123
|
|
Author review |
Overall Rating | | 6 |
Professor Rating | | 6 |
Interest | | 6 |
Easiness | | 6 |
Average 60%
|
|
|
|
Sfwr Eng 2s03
The course was designed to give understanding to the basics of programming and show the different types of programming languages with their individual features. Our prof Dr. Farmer, gave special attention to lesser used functional programming language paradigm, with a more specific passion for using OCaml. After taking ENG 1D04, most were used to the comforts of a nice drop-down menu with tons of visual features and easy object-oriented programming, but because of the attention given to OCaml, this was a rude awakening for most. About 90% of the material taught throughout the course was shown using OCaml programming code, which was difficult because the syntax was so different from any of the popular and more commonly used languages, (C, C++, C#, Java, etc).
It seemed as though Dr. Farmer split the course concepts into two main categories: the Functional Programming Paradigm (OCaml) and the Imperative Programming Paradigm (C). Topics included the advantages of using either type of programming paradigm as well as features that are either offered in one or the other or even both, such as lists, tuples, arrays, linked-lists, nodes, etc. A major concept was data structures of inserting/modifying/deleting data within programs, which was carried through both types of programming paradigms.
Mark Breakdown
I-Clicker Quizzes - 20%
Programming Assignments - 20%
Midterm - 20%
Final - 40%
There were ten in-class quizzes, and they were a pain. Lecture was 8:30am and he would have them at the beginning of lecture on Fridays, which sucked! They consisted of five questions which usually had more than one answer and thus caused tons of confusion and argument after he took them up.
There were also six assignments, four of them devoted to OCaml programming, showing a glimpse of how much that man loved that language. They were all about vector storage, i.e. storing 2-D vectors like <2,2> in the Cartesian plane and modifying them or keeping track of the largest magnitude vector, and lots of other stuff like that. They weren't very interesting and in the beginning they were rough because OCaml was hard to grasp at first. The final two assignments were written in C but were under the same guidelines, vector stores. They were a lot easier though because there was a lot more information regarding coding in C rather than OCaml.
The midterm and final were somewhat similar with a bunch of multiple choice questions on basic knowledge of programming concepts with a few small code debugging questions, and the last couple questions were to hand-write programs on paper.
The OCaml textbook was a pdf online and was pretty vague on specific errors and the majority of issues that people had with it. The textbook for C, "C Programming: A Modern Approach", by K. N. King was an absolutely great foolproof reference and I still use it to brush up on stuff now.
All in all, the prof was good but chose the wrong approach for teaching programming principles with useless programming paradigms for the real world. Ohhhh Caml is right!
|
|