| Faculty: | SCHOOL OF COMPUTING | Academic Year: | 2005/2006 |
| Department: | COMPUTER SCIENCE | Semester: | 1 |
| Module: | PROGRAMMING METHODOLOGY (ENGINEERING ONLY) - CS1101C |
| Qn | Items Evaluated | Module Avg Score | Nos Responded |
|---|---|---|---|
| 1 | Overall opinion of the module. | 3.623 | 512 |
| 2 | Grade likely to get for the module. | 3.783 | 503 |
| 3 | Difficulty level of the module. | 3.945 | 512 |
QN\SCORE | 5 | 4 | 3 | 2 | 1 |
Qn 1: Overall opinion of the module. | Excellent | Good | Satisfactory | Unsatisfactory | Poor |
Qn 2: Grade likely to get for the module. | A | B | C | D | F |
Qn 3: Difficulty level of the module. | Very Difficult | Difficult | Average | Easy | Very Easy |
| Nos. of Respondents(% of Respondents) |
| | | ||||||
ITEM\SCORE | | | Excellent | Good | Satisfactory | Unsatisfactory | Poor |
| | | ||||||
Module | | | 68 (13.28%) | 240 (46.88%) | 157 (30.66%) | 37 (7.23%) | 10 (1.95%) |
Module at Same Level (Dept) | | | 194 (13.59%) | 592 (41.49%) | 477 (33.43%) | 129 (9.04%) | 35 (2.45%) |
Module at Same Level (Fac) | | | 306 (11.37%) | 1174 (43.63%) | 970 (36.05%) | 185 (6.87%) | 56 (2.08%) |
| Nos. of Respondents(% of Respondents) |
| | | ||||||
ITEM\SCORE | | | A | B | C | D | F |
| | | ||||||
Module | | | 95 (18.89%) | 242 (48.11%) | 132 (26.24%) | 30 (5.96%) | 4 (.80%) |
Module at Same Level (Dept) | | | 300 (21.41%) | 606 (43.25%) | 349 (24.91%) | 116 (8.28%) | 30 (2.14%) |
Module at Same Level (Fac) | | | 533 (20.22%) | 1346 (51.06%) | 576 (21.85%) | 148 (5.61%) | 33 (1.25%) |
| Nos. of Respondents(% of Respondents) |
| | | ||||||
ITEM\SCORE | | | Very Difficult | Difficult | Average | Easy | Very Easy |
| | | ||||||
Module | | | 114 (22.27%) | 272 (53.12%) | 112 (21.88%) | 12 (2.34%) | 2 (.39%) |
Module at Same Level (Dept) | | | 343 (24.02%) | 718 (50.28%) | 318 (22.27%) | 42 (2.94%) | 7 (.49%) |
Module at Same Level (Fac) | | | 425 (15.79%) | 1048 (38.94%) | 1075 (39.95%) | 126 (4.68%) | 17 (.63%) |
| Q1. | Please comment on the strengths and weaknesses of the module, and suggest possible improvements. |
| 1. | is hard and too many to study |
| 2. | interesting.increases awareness about computer programming. |
| 3. | Interesting but can teach more for practical uses and less theory. |
| 4. | Lab should have a smaller time limit and greater percentage to reward better students rather have everyone scoring approx the same even if one i much better than the other. |
| 5. | Good pace. Could post full solutions to all the tut questions. |
| 6. | Too many things to learn in such a short period. Lab session can should start at day time instead of 12am. ie. 8am to next day 8am. |
| 7. | - Weightage of PE should be reduced to say 20% and distributed to the labs say 10%. - There should be answers to non-asterisk questions in the tutorial. |
| 8. | The Lab part of the module is difficult and time comsuming yet the allocated module marks to the lab is not in proportion. |
| 9. | The time spent on doing tutorials was a lot more than the time spent on the tutorials of other modules. This module is quite interesting and sometimes fun, but understanding the concepts is not easy. This module has certainly taught us the basics of simple C programming which would be beneficial as an additional skill. |
| 10. | I find the module too demanding. Not only are there weekly tutorials, we have alternate weekly assignments with 2 exams at the end of the sememster. It's a real disadvantage for students with negligible background in this module. I realised some of my classmates with little or more background in programming, picking up the module real fast which is a unfair for people who have nothing to fall back on, thus they are able to score well. |
| 11. | Try to emphasize that this modules is not easy at the beginning, and it is important to have a critical thinking in this modules to students at all the time during the semester. |
| 12. | Good introductory content. Lecturers generally clear. However slides were basically rewritten versions of the recommended textbook - maybe an ALTERNATIVE description of concepts would have been more useful. |
| 13. | The lecturers are too rush to finish the syllabus! |
| 14. | This module is difficult because most of the time we have to practise ourself,it wastes a lot of time.Sometimes, if you are not familiar with it, you just cannot program even if you finish the whole book.But i think overall is satisfactory. |
| 15. | Strength : interesting Weakness : pace of this module is too fast, too demanding, and too confusing for a beginner in programming. Possible improvements : longer lecture hours to allow a slower pace. |
| 16. | THIS MODULE IS QUITE HARD FOR STUDENT WHO HAVE NO KNOWNLEDGE ABOUT PROGRAMING BEFORE.THERE IS A LITTLE CHANCE FOR PRACTICE |
| 17. | The deepth is okay. However, the knowledge told in lectures is simple. The exam questions are much more difficult. |
| 18. | i think the module should concentrate more on labs that concentrate more on basic c programming... |
| 19. | The module is very interesting but due to lack of time the last few important chapters have been rushed. |
| 20. | Should have webcast. |
| 21. | I would have liked Raymond with us all the way. Nonetheless, it is no one's fault but mine if i do not perform to expectation. I realised that one has to have some idea of the lecture before attending it so that all the technical jargon that is discussed won't be as foreign. Close follow up with the tutorial is necessary. LEcturers were good. Module was in fact manageable. I just needed more discipline |
| 22. | The last few chapters were taught in too short a time. The lecturer was patient the forum was active. |
| 23. | mid term was really complicated as opposed to general tutorials or questions seen. Usually difficult problems are not eplained but are encountered during labs/exams but i guess its the nature of the course material. overall, useful module. Learnt quite a bit. |
| 24. | More real time examples should be demonstrated for the 2nd half of the lectures(6 onwards) |
| 25. | The latter part of the course, which seems more dificult and challenging, had the lectures conducted by a relatively inexperienced lecturer. We should give the new lecturer some support no doubt, but I believe having him conducting the first few lectures for the module is much a better arrangement. |
| 26. | 1st lecture (Raymond) is good, the same cannot be said for the 2nd lecturer, but I think it is because he is inexperienced. My tutor (Henry) is superb, gives very detailed explanations that are very easy to understand. Regarding the midterm mcq test, I feel that it is not a test of concepts, but rather the questions are there for you to spot tiny weeny errors that people tend to overlook, but then since the programming code in the questions lacked good programming practises, it is actually lousy code, and we are supposed to find the flaws in lousy code. What do we learnt? I learnt the importance of good programming habits, that's all. Yar, thanks huh. So personally I think there is a design flaw in the mcq test. On a sidenote, I personally feel that the test setter's main aim was to attack our weaknesses rather than to give a fair assessment to all students. Please do not take it personally, as I do not even know who the setter is. |
| 27. | The lab sessions are interesting and provokes thinking. It allows us to apply what we have learnt in the lectures. However, think the time given to complete the Lab practical exam may be too short. |
| 28. | It gives a very good introduction to a person who has no previous background on programming. Although personally, it deeply puzzles me using "C" as the choice of programming language. NTU has already phased out the use of "C" programming language and A-Level Computing (4 years ago) uses the more advanced "C++". I suggest changing the choice of programming language to the more updated Java. Topics such as Object Oriented Programming can be introduced easily. |
| 29. | Too many things too little time. The notes and textbook do not give sufficient materials about tackling programming labs. |
| 30. | there is simply not enough time given especially for the final practical exam. |
| 31. | this module is not really easy but not too complex too. the applications are really huge. |
| 32. | For lecture notes in the later part of the module, maybe should try to include complete programmes as examples, instead of giving just functions. It helps varify some doubts (eg. what header files to include, how the functions are called in the main function) |
| 33. | strength - informative weakness - teaching pace too fast. hard for beginners to absorb improvements - more hands on examples |
| 34. | This module should not be made compulsory for all students. The final practical should be remove. Reason being that all the difficult things to be learnt in this module was ruched through like a bullet train in the last few lectures and we are expected to apply them in the end of year prac. |
| 35. | Strength: The lectures notes are comprehensive and clear. Possible improvement: More time given for lab assignment |
| 36. | The lab question released on 0000hrs every wednesday is taxing on the students as most would stay up to complete them. I would suggest the question to be released at 0000hrs on friday as saturday is a non academic day for most students. |
| 37. | I think this module is necessary for all engineering students and I am glad I got to learn this new skill of C programming because I think this module trains students to think creatively and learn to solve problems on their own instead of depending on the teachers. |
| 38. | The main weakness of the module was that it had to cover so many topics in such a short time. People without any background of programming would have a really tough time, and this module would take up a lot of time. The lecture notes were nicely written and split up, but would be even better if it was more in detail. |
| 39. | I find the change of lecturers halfway throughout the module a bit disruptive, and that the more important parts of the modules such as arrays and structures a bit rushed through eventhough the section is important as we use them mostly in labs and practical exam. |
| 40. | not enough time given to fully master the module well. |
| 41. | notes and lectures are organized. available webcast made it more convinient and flexible |
| 42. | The most difficult module I've ever studied !!! Totally lost ... I used to love programming , now it's my nightmare since I HAVE TO STUDY THIS MODULE . |
| 43. | In my case, i see my tutor is not well qualified to teach the subject. The amount of questions that are discussed in the tutorial classes is too little. Actually, we are given solutions to only a few questions that are set in the tutorial sheets. This should not be the case. Solutions to ALL questions should have been provided. |
| 44. | - Should increase the time for PE to ensure we students have enough time to cover the question. |
| 45. | the lab questions are generally difficult, many including me had to spend many many hours completing them. That wastes us a lot of previous time and discouraged. |
| 46. | It is a interesting and brain-training course. I felt very impresses with the function of the computer after i acknowledge C programming.Thus,I'm thinking of taking another related module next semester.Thanks to my lecturer+tutor Mr Raymond Tan.Full respect and gratefulness for him in helping me in this module. |
| 47. | More practical problems Less tricky questions in tests |
| 48. | i suggest that more lab seesion being provided as i have no prior experience in the programming and i find hard to cope with the module.i hope that i can have more practical exercise especially lab session. |
| 49. | This module is good for those who like programming. |
| 50. | The time allocated is too short. |
| 51. | This module is fun and useful. However, i dont like the change of lecturer after the mid term break. The tutorial problems are also too abundant for me although i was not required to do all. |
| 52. | Strengths : Weaknesses: Difficulty |
| 53. | It is a very usefull module for future. |
| 54. | I like the way labs are conducted as it gives me adequate time to think about the problems and how to approach them. |
| 55. | I believe more tutorial hours are needed to help non-programming background student. Other than that, satisfactory. |
| 56. | well, this module is quite tough for me since it is completely a new way of thinking and setted in the first semester. |
| 57. | it is better to have some more practical lessons instead of tutorial lessons |
| 58. | This module is very hard to understand, it needs a lot of self practice, so if it is possible, this module should have more practical tutorial and lecture. |
| 59. | This module is very good to train logical and structured thinking. |
| 60. | interesting module, staff are helpful, but standard of tests are too high for majority of students. maybe if possible could instead of moderate student's marks, moderate the difficulty of tests? but not too easy nor too hard. |
| 61. | I do not have any background on programming, but after going through this course, it makes me feel interested about programming(other than the exams). Basically, i feel that this is an interesting but difficult course. |
| 62. | Good for engineering students as an introduction to programming. However, this programme is rather outdated. A newer language should be thought. |
| 63. | Strength:interesting to code Weakness:Difficulties |
| 64. | The questions in tutorials and the ones asked in the exam are extremely different.The level of questions in tutorials should be increased and more exam-type questions should be included. moreover the time given to do the practical exam and midterm test is insufficient to complete the exam(atleast for a normal average student). it is more like a rapid fire test. |
| 65. | Good lectures. Good tests. |
| 66. | Lessons had been taught in such the way that all students are assumed to have the basic knowledge about pragramming already, which is very untrue. |
| 67. | Generally ok |
| 68. | interesting module for an introduction to the world of C pogramming. |
| 69. | Module is difficult to understand for beginners. Need more time to study this module and work on it. |
| 70. | for students who do not have computing background will find this module very tough. More time could be allocated to the practical lab though |
| 71. | Should have longer or more tutorial sessions. |
| 72. | i feel that we should be given more time in our prgramming lab. Say 2hrs 15 mins. |
| 73. | This module should have covered more topics on C programming (such as memory allocation, linked list) so as to provide a better foundation in algorithms for the students. |
| 74. | Learning curve very steep, especially for beginners. |
| 75. | i feel that there should be more attention catered to the students who do not have computing background. |
| 76. | Solutions of every tutorial questions to be uploaded into IVLE instead of just a few selected ones. |
| 77. | It focus too much on the compiling part and debugging, expecting human beings to be as capable as x86 or unix machines. Less emphasis on debugging in normal exams because debugging is a natural process in Practical Exam and labs. More labs is needed as i feel a lot of students do not have enough practice since programming is all about experience. Also why is CS1101C and not a java course offered to the engineering students since java is the 'in' thing now and a lot of industrial companies will be shifting to java. Now I have to find a java course to take ... :( |
| 78. | Weakness: No on-the-fly lecture assignments. |
| 79. | too many generalisation of topics which are no really relevant.. |
| 80. | The module is taught at a comfortable pace for students with no prior knowledge of C Programming. |
| 81. | TAs should be carefully selected. Some TAs cannot teach although they have sufficient knowledge. A large difference in PE and normal lab sessions. Labs are inadequete preparation for the PE. Lecture notes are well prepared |
| 82. | The reduced syllabus is a comfort, and this will allow students to better concentrate on the fundamentals - advanced content should be covered later. The lack of a webcast for this semester's lectures has not affected me much, but I think it would be a good idea just in case students need to review this lecture later on. Maybe selected webcasts can be provided. |
| 83. | The 24-hour lab session on every wednesday is a good idea, so that lab attendance is not compulsory. However, I lost lots of sleep pondering over the questions which are not so straight-forward. |
| 84. | hope that students have more practice on lab, practical exam style questions, as tutorial questions are insufficient practices are they are more of for learning uses than practices, as the tutorial questions are mostly in parts which are not the same as practical and lab questions |
| 85. | Too much is being taught at a very short amount of time. Programmming is not meant to be learnt from text books and reading. It is heavily practice intensive and requires a decent period of time to master, especially for people with no background. This module greatly dampened whatever little interest I had in programming in the first place. I am presently studying in computer engineering(FOE), juding from this module, I am greatly diillusioned on the prospect of CS1102C and the discrete maths module. This course made me understand why there is such a strong resentment towards CS modules by many of my seniors. This module should be split up into 2 modules or at least introduce a compulsory module just to teach the fundamentals of computing such as debugging. The A level computing course took two years and yet taught on less than what the CS1101C module covered. One reason was probably that many other things such as fundamentals were taught instead. |
| 86. | A very through and structured way of learning. |
| 87. | Good teachers and notes probably have to emphasis that it's more of a hands on module |
| 88. | The testing format, in which students are expected to reproduce the output of compilers, seems rather useless especially as most students will not be using the language in future and hence would not need to memorize the particular idiosyncrasies of C. A better way might be to test the logic and concept behind the program. |
| 89. | Not enough practice questions for us. |
| 90. | topic on structures was too rushed. |
| 91. | lots of time needed for practice. |
| 92. | i feel that students that have taken Computing as an A level module (and have achieved a satisfactory grade) should be allowed to skip this module, as the syllabus is vastly similar. |
| 93. | strength: very detail and useful of the lec slides weakness: fail to go into depth on some of the more difficult topics |
| 94. | lectures were fast. |
| 95. | The lab questions are very good and interesting. |
| 96. | Having it as an open book module is really tough....But this also an advantage because it makes us think rather than memorize unneccesar facts... |
| 97. | Could not make any comments as i am new to these system |
| 98. | This module is really good for beginners in programming. |
| 99. | Basically to my concern,i had science background till my A level.So i find it difficult with this module.And BTW, to my suprise the module is difficult enough for me till now.The labs and the practical exam were so tough to me .Though its neccessary to learn as a computer engineering student ,C program is a vast subject which could be learnt for atleast 2 semesters. |
| 100. | i feel that it is very difficult, since i have no computing background..... |
| 101. | The labs and tutorials help us in logical thinking. Even though it is a bit tough, i think this module betters the student in the language. |
| 102. | It is quite difficult for first time programmers and the upper hand that the people who have experience at programming is quite unfair |
| 103. | Easy to understand but quite difficult to apply while programming. Improvement: Need easily available friendly tutors and lecturers. |
| 104. | I think the module is more practical than written. Hence i think the lecture way may not suitable. |
| 105. | Fortunately, the notes are pretty informative. Keep it that way. |
| 106. | This module is excellent because we have managed to learn a new skill compared to other modules which are just part and parcel of something else. |
| 107. | A lot of time needed. Not enough information passed to us and yet expect a lot from us. |
| 108. | time is often not enough for us to complete the tests, exams... |
| 109. | pace of teaching fast. pls slow down a bit. |
| 110. | Many topics are covered in too short a time. However the tutors for this module are very interesting and they make this module an interesting one. |
| 111. | Strengths: This module was constructed in a very organised manner. It covered the most important topics of programming and was taught in depth. It proved useful to me as i was applying the knowledge in other fields of study. Weakness: The change in lecturers was very sudden and because this is a new area of study for most of us, we had a hard time trying to adapt to the new style of teaching. Suggestions: Try to allocate one lecturer to one group for the whole semester. Then, for the next semester, the other lecturer can take over the entire group. |
| 112. | programming is like learning a foreign language with a lot of technical stuff to remember. i thought it would be better if the module was reduced so that we can have more time to process and absorb the things we learnt. |
| 113. | Nil |
| 114. | The questions posted to us are interesting. Probably, the speed of lecture could be faster in the earlier chapters so that we have more time for the difficult part at the back. |
| 115. | The module fosters critical and logical thinking. |
| 116. | Interesting, I'm satisfied |
| 117. | maybe can teach more on how to come out with a main structure which is more important especially in complicated task. |
| 118. | It is interesting but also quite demanding at the same time. |
| 119. | plesse teach about how to programm a game. |
| 120. | provides fundamental knowledge of programming. |
| 121. | It is quite difficult for beginners who have no prior knowledge to grasp the concepts. I feel the pace of the lectures was a bit too fast. |
| 122. | limited lectures. |
| 123. | provide fundemental knowledge of programming |
| 124. | Strength: The lecturers prepare their notes as well as the lectures quite well. Weakness: The time for the release of new lecture notes is always a bit late. |
| 125. | more examples will make it better |
| 126. | It is quite all right. suggestion:Maybe another text book will do better than the current one . |
| 127. | The tutors should standardise the ways of judging the level of participation amongst students in class. |
| 128. | very short time to master all the different techniques necessary for future uses... |
| 129. | Quite complex. Especially for new students taking the module. It should be divided into two semsters. |
| 130. | There wasn't enough time to finish the last few chapters of the module in details (insufficient examples). |
| 131. | We have a good lecturer in Mr Raymond Tan. |
| 132. | This course gave me a better understanding of what computer programmes can be produced and utilised to solve problems. Strengths: Systematic Weaknesses: More past year practice papers |
| 133. | Strength is to allow us to be more flexible and aware of the future challenges ahead of our uni life. Improvements: Kick away the the idea of doing Lab sessions with the privilege of doing it the whole day. Instead, make it a 2 hr session to let the students be more well prepared for the PE. |
| 134. | lecturer should occasionally type simple programs to demonstrate ideas, instead of talking on about it. |
| 135. | Good pace, lots of resources available. Marking of tests and labs is efficient. |
| 136. | I do not like the way the topic is being tested. It requires us to step away from the computer to do a written test, but that is not how programming is done. Trial and error should be allowed in front of the computer. |
| 137. | UNFAIR! THose people with prior knowledge of C programming should be precluded from taking this module |
| 138. | I would prefer that the module teach we also how to debug programs, so as to be able to write and compile successful programs within a short period of time. This is because most the the time spend in writing a program (for me) was spent trying to deciphyr the errors. |
| 139. | The sequence of the Loops, condition and test statements shouldbe taught. |
| 140. | hard to absorb anything in a lecture theatre room environment. would have been better to hold classes in smaller groups in labs. cos tis is programming! need to ask plenty of whyss.. |
| 141. | More examples need to be given. |
| 142. | C programming is tough especially for students who have never taken such courses before. Perhaps the introduction of every topic can be more elaborated and include what can be expected from each topic. |
| 143. | The second lecturer has much room for improvement. |
| 144. | The module allows people with no computing background to learn something new. However, it creats a high stress level for most people i know because of the lab sessions. Maybe the lab sessions can be slightly modified. |
| 145. | The strength of this module is that a seemingly small syllabus is tested thouroughly, so as to fulfill the purpose of understanding the methedology of programming. |
| 146. | This is my favourite module. I think this module would have been even better, if it was taught by a single lecturer the whole semester. |
| 147. | shouldn't commence it for 1st year, 1st sem |
| 148. | very hard to understand....too logic..not suitable for girls.. |
| 149. | it's a bit unfair that quite a number of people did C programming before.Of course for those for a new to programming, they can't really catch up.and the teaching pace is too fast. i think the university should not allow those who have any programming background in their academic records to take up this module. i think this module is too hard except for those who really likes programming, those who are smart,and of course for those have programming background. the syllabus is just too hard for most of the people.too few hands on learning.we are all get stressed by the labs and PE.which many of the people can't really do it. it makes everyone hates it.and thus how will the teaching and learning environment in NUS be efficient?this is just downgrading the university reputation. at least make this module into a few difficulty level.for those with programming background, keep them away from the easiest level.so that it's fair for everyone. webcast all the lectures please |
| 150. | I think the practical exam should not be set extremely hard. 1 hour and 45 min is not enough to finished compiling the program for someone who does not have knowledge in programming b4. Students who could finish the PE are those who have learn programming b4. |
| 151. | strengt- it make students think critically - good lecturer weakness- only tutorial solution for certain questions are given improvement - more marks should we counted from lab sessions for the averaall grade of the module compared to the practical exam. |
| 152. | More CA marks for lab sessions because 5% for all the hard work is really very little. |
| 153. | Racy portions, even though they have been reduced. Takes up a lot of time. |
| 154. | The strength of this module is that it is more practical and applicable to the work industry after graduation. Another thing is that it gives me and those people that has zero background in programming, a better understanding of how a program is created. The weakness is that this module is quite loaded. With the time given, some of the students are not able to catch up as the C language is totally new. I would suggest to cut down on the syllabus. |
| 155. | This program is indeed very difficult for me. The workload is considered heavy and i feel that there is an unbalanced weightage of the workload. |
| 156. | Weak in explaination, practice and exercises. Good at the knowledge, that means we have lots of unknown-knowledge in this subject |
| 157. | Lecturer should give us more exercises to do such as more labs and so on. |
| 158. | It is a quite good module. |
| 159. | slow down ,don't too fast~~ make more example~ |
| 160. | this module is very hard,need a lot of time,but it is very interesting |
| 161. | i think some programming thinking should be introduced into this course. |
| 162. | Because of lacking basic background knowledge, I think i really had a difficult time. And i think we should have more lectures. |
| 163. | The strengths are out lectures and tutors are very responsible and patient.The weaknesses are there are not enough labs for us to practice. |
| 164. | The content of tutorial of principle of economics shoud be harder,so i feel better during the examination.The english of Electrical engineering should be improved .i can not catch up with him |
| 165. | Content of the module is easy to pick-up when one has some basic programming knowledge. However, test question occasionally appear to be questionable esoteric. |
| 166. | n.a. |
| 167. | 2nd half of the sem was going too fast. There's little time to really understand the new chapters. Or maybe it's just us students who don't spend enough time studying... |
| 168. | The weightage of the practical is way too much compared to the labs. 25% for PE is not fair for those students who have no background on programming. Moreover, the time spent on the labs are way too not worth the 5% for all the labs sessions, especially for the newbies. I believe that the aim of this course is not to test on students on how well they can come out with a program within 1hr 45mins(PE), or rather if students could understand how C works and how they can come up with a program to solve the problems using C, emphasis should not be on the time basis, but on the ability to do that. Being able to program in such a short duration in a PE is not quite fair to the programming newbies, for example, if the newbie encounters a very rare error or mistake in the PE, they might not be able to debug that as efficient as the others, and thus stuck in the process, which results in losing a lot of marks as they are inexperienced on what to do if their programs are stuck somewhere. I propose that the efforts for the labs should be more recognised and be placed for more weightage. In turn, weightage of PE should be reduced to the minimum(about 10%), as students should be tested on how well they understand of C, rather than testing their on time, which is not quite fair to the students who have no background on programming and yet have to be able to program well and fast within only 3 months of study despite having to handle other modules at the same. |
| 169. | since its a module that is rather new to most students, a good lecturer is really needed to let us understand the module better. |
| 170. | Comfortable starting pace, which is good for the students who do not have a programming background. However, the pace picked up very quickly at the later part, and it was more difficult to keep up. |
| 171. | insufficient learning time for students who do not have prior knowledge to this module |
| 172. | Strength: Allow us to get exposed to the world of programming. Weakness: Time is too packed for such module. |
| 173. | more emphasis on the later topics. |
| 174. | It is suitable for students with or without computing background. However, students with computing background tend to have an edge over those who don't. The percentage for the lab is too little. (5%). It should be increased. |
| 175. | This module give students who dun have programming backgrounds a good introduction. The biweekly programming assignment forces students think through and to solve the problem. |
| 176. | Provide more concrete examples of full progams, highlighting possible misconceptions and errors. |
| 177. | good |
| 178. | Regarding tutorials, I suggest that solutions should be given for all the questions in the tutorials instead of only the questions marked by a * . |
| 179. | The lectures are well planned. Sufficient links and help are available through ivle. |
| 180. | The course was interesting, and lecturers tutors were all very nice. |
| 181. | Strength-Learnt alot of things Weakness-Module did not prepare us enough to answer the Lab questions. This is based on the previous years practical exam. |
| 182. | Run the programme on the spot instead of just showing the code in lecture... how noes whether it really work not. The tutor are quite responsible in class however they should try to bring attention to important things that we may neglect as we also have no idea what we are not aware of instead of just going throught the tutorial questions. |
| 183. | The labs and practical exams, though difficult were inspiring...This is the only module which gives the surety of becoming a professional engineer |
| 184. | This module introduces us to the world of programming but those who have previously done programming are at a very distinct advantage.Anyway a very esse ntial module and an engrossing one too. |
| 185. | Some of the lecturer was unable to bring the point across clearly. Such that i was unable to understand the topic well. For the tutorial class, honestly speaking, the tutor was also not able to teach well. |
| 186. | can have few more hours for lectures and do some programs and compile in the class so that we can approach the subject with more confidence. |
| 187. | this module is difficult for students without a background in programming. the concepts are difficult to grasp and apply without proper practise and experience. |
| 188. | It is a very good module for us to learn programing. However, the exam is really tough, especially the practical exam which gives only 1 hour and 45 minutes. I think we should be tested on how we think to write a program and not how fast we can write. |
| 189. | The time is not enough for students to master the lessons. For the students who the first study programming, I think they get a lot of difficulties. This is not the first time i study programming but i still have some difficulties. Some of my friends are scared of this module. Actually, for programming, practice is very important.But we must study other modules, not only CS1101C. I wonder whether the students who first time study this module understand the lessons or not. I can see some their innocent mistakes. |
| 190. | Give more exercises and make lecture more interesting....such as explaining the concepts with more programs, not just explainingt the slides only.... |
| 191. | The questions are vigorious. However, I do not really fancy the switch of lecdturers midway thgouth the semester. The forum of this module is very helpful and supportive. |
| 192. | Have more programming sessions as it would then be mandatory for the students to practice and be assessed, hence improving provess at programming |
| 193. | The module teach the students high en programming.But it is definitely impossible for stuents like me who dont hav previous experience in C.They say that the previous experience is not necessary but without previous experience it is a hell to study that module. Teh practical exam adn labs are damn tough.I think personally that none can finish the PE in 1 hour 45 minutes.But there may be genius students who do it.But is NUS only for Genius students like them ? C is a big language an it cant be completely read in one semester.Atleast they can make the duration of stuy of the module to 2 semesters instead of 1.So that we can learn deeply and also easily.In indian universities we hav C but for two semesters. |
| 194. | more weightage on practical. |
| 195. | my most interesting module this sem though.. it's easier by a mile than the SoC's (CS1101X/Y/Z) expecting one like that.. |
| 196. | Although our lecturers claim this is a module suitable for beginners at the exam we are tested on complex algorithms rather than on the newly learnt commands of the program. This appears to me to be very demanding. In my experience I had to put much more than 7 hours per week into the module. Also near the end of the semester, many difficult topics were taught for which I could not practice enough before the exam. |
| 197. | I am a no-voice with regards to programming. But even then, I felt that this module was really good and challenging.Though it is undeniable that the module is damn hard, I must admit that the lecturers and the tutors have done a great job. |
| 198. | The module efficiently introduces the programming language and also provides exposure to programming as a whole. However the assesment should be more continous; Labs and Tutorials should have more weightage. |
| 199. | This module can be said effective because it can give a lot of knowledge with C programming within a very short time of about four months. |
| 200. | An interesting module which is made even better by the great teachers. |
| 201. | The questions set for the practicals are of the highest standard... That is good... However, when it comes to theory exams, I find some of the questions a little redundant as they require you to manually (using your brain) to compile and run the program given... |
| 202. | I think the number of labs is very small. The number of Labs must be greater so that we have greater practice of good questions. Also the Practical Exam time must be greater |
| 203. | This module is good in stimulating our thinking skill, but the test and exam are too hard for most of us. I know that there are always some students who can score almost perfect in the exam, but setting the level so high will just cause most of the students to score low, ruining their interest in programming. |
| 204. | The syllabus is too packed at the end of the semester. In addition to this, most of the important chapters are left until the end of the semester. Hence, this makes it to be more difficult to cope with. |
| 205. | Lab and practical exam too difficult for me! |
| 206. | PE is rather difficult. Try to make the module more workable. |
| 207. | too few practical. |
| 208. | helps develope way of thinking logically and systematically. should have consultation hours, source of exercises. |
| 209. | The exams are too tricky and difficult, for people like me who are doing programming for the first time. The duration of practical exam is too short. |
| 210. | The second half of the semester's lecture should improve on explanation of functions and stuctures. |
| 211. | Interesting module however the multiple choice questions tends to be very tricky. And the programming lab is very time consuming. Took up a lot of time and not much time left for other modules. so lab session should be given extra marks. because it is quite unfair if students can do lab questions (know how to program) but cannot program fast during PE. also the marking scheme for PE is flawed. 30 marks shouldn't be given to marking output. because if the program doesn't produce the right output but it has majority of the parts working well, then it will not be fair. What is important is the process not the outcome. |
| 212. | as this is my first proogramming module, the time for revision is too short. exams come as soon as lecture finished. |
| 213. | er...v good alr.. but i am weak... no time to practise.. this problem cannot be solved by tutor i guess... |
| 214. | I think the explanations each lab section can be added in the suggested solution, it will help us to understand it better or improve our programmes. |
| 215. | very hard for beginners,can give more labs for practice |
| 216. | Generally, I feel that it is hard to apply what I have learnt in lectures to real practices. Maybe more hand-on-hand teaching can be implemented to guide individual student one by one. |
| 217. | The module has less time for us to practise. Though it is true that we have to practise on our own, but the resources to practise are not much. Tutorial answers should be provided for all questions. The strength, i benefits from the module in the sense of soft skill, the way i think and i can apply the skills in real world problems. The weakness, i felt that students are not given enough time to really understand the concept. Again, it is true that we have to work it on our own, but the guidance is not there. |
| 218. | Much of what we were taught towards the end of the semester will not have been tested through the weekly laboratories. Perhaps have 5, instead of 4, weekly laboratories or finish the syllabus faster. |
| 219. | Strenghths: The module is well paced and is taught from easy in the beginning to harder steps as we gain more experience. This module has done a good job in condensing such a vast subject into the short time period we have. The flexible labs are good practice and the deadline is appropriate. Weaknesses: The Mid-Term exam should perhaps have tested students more on understanding the concepts rather than on observation skills. Rather unfair to students who have just started learning C. Plagiarism checker still rather strict. Many "innocent" students are still caught. Suggestions: Plagiarism checker should be more lenient since the lab's main purpose is to practice programming and not make sure we all have different programmes. This is not unreasonable since the lab's percentage is only 5% and also those who copy only make their lives more difficult during practical exams. The webcasts should be more updated and also be sure to include all the topics covered(some are missing as of now). |
| 220. | The pace of the module is very good. Concepts are simpler in the beginning which allows even a beginner - having no prior knowledge of computer programming, to understand the concepts easily. The course is designed keeping in mind the fact that knowledge of programming is not a pre-requisite. However those who have done it before, they might find this module easy. Tutorials are comprehensive in the sense that even the smallest concept is tested. Each program tests on a different concept. Thus, covering the whole chapter. The labs are really interesting - testing the major concepts. We start thinking at a higher level while solving the problems. |
| 221. | The lecturers are very professional and the arrangement of CA keeps students studying. |
| 222. | N.A |
| 223. | give some hints when having PE. |
| 224. | the hard topics are taught too late and we are given too little time to practise them and use them in the exams. on the other hand, we spent quite long time on the very simple topics. |
| 225. | After mid-term, things turn to be difficult. There should be more time being spent on that. |
| 226. | tutor is not responsible enough. |
| 227. | Too little time to the last chapters, which is also the most difficult and requently tested. The first half part should move faster!! |
| 228. | I think some parts like pointer,array,structure are difficult. I think more exercises would be better. |
| 229. | Generally good! |
| 230. | The module is good, but the last several parts are gone through too quickly. |
| 231. | shoule be more practice |
| 232. | I think it is very difficult ,I have a lot of difficulties about this module. |
| 233. | more past years's paper and complete solution for tutorials problems will be helpful. |
| 234. | i cannot learn too much duringthe tutorial class. |
| 235. | No |
| 236. | This module is quite ok generally. strength, the lecturer Raymond Tan is quite competetive and so is the tutor Henry Chia |
| 237. | Quite useful especially for engineering applications, but a bit hard. For example, got only 1h 45mins in PE, not enough... |
| 238. | This year they reduced the syllabus,so the module appeared to be easy,but very hard to differentiate among students.I prefer last sem's syllabus,although it is hard to follow and workload wil be more..... |
| 239. | unfair judgement about lab plagiarism. |
| 240. | Weakness: Practice is much easier than exam. As a result, we cannot get a high grade. Suggestion: Increase the quality of the tutorial question. And increase the difficulty of the questions. |
| 241. | At the beginning of this module, several lectures have focused on some basic concepts like initialization. At the end, there seems to be insufficient time for us to learn more advanced things like arrays,pointers and structures. As most of us had some knowledge in programming before, I think maybe the first few lectures could be reduced and more focus could be placed on later part in the syllabus. |
| 242. | thought a bit diffcult ,i can mangage it. |
| 243. | It is quite well taught. |
| 244. | well i feel that we should have had the same lecturer through out since i havent understood anething beyond arrays! |
| 245. | I find no use of being taught this module when in the next semester we will be taught C++. Instead of teaching us C programming, we should be taught C++ directly in the first semester, as it is a much more advanced and better language than C. Moreover I am dissatisfied with using the Unix based system for this programming module. Why not use a simple widows based environment which is more user-friendly and allows the person to concentrate more on the coding rather than to waste time on learning the commands of a new operating system. |
| 246. | with respect to syllabus this module is not very hard but exams questions are set to be very hard assuming students already have knowledge some of them do but as there is no prereq for this module it should be for those who have no background in programming plus there is really lack of practical experinece for example lams etc |
| 247. | The planning of this module was excellent...plenty of tutorials and worked examples really helps us...The tough lab questions really challeneges our intelligence.Simply the Course struvture is very good..But the fact that some students like me do not have any background in programming find it difficult to understand the whole set up in few days.May be thats the reason i foud this module "satisfactory" |
| 248. | The recomended book gives a basic idea of programming. But it has less explenations. Better to recomend another book. |
| 249. | Strength: the lecturers and tutors are very competent. They can give the material clearly. Improvement I suggest: The module are moving very fast after the midsemester. If it is possible, try to divide the material more evenly, especially as the materials are getting more difficult later in this module. |
| 250. | The strength lies on its purpose-to help student with understanding programming. The weakness is that this modules always requires much knowdledge which wasn't taught in class. I suggest that this modules'd better test what was taught |
| 251. | I think the lectures at the end of the semister were not tought properly.I think we should have more CA at regular intervals. |
| 252. | It need a lot time to practice. |
| 253. | The Test is tough. And you are killing me soon with the practical. My favorite modules, but unfortunately I just do not score that well from it. |
| 254. | I feel that the mid-term test for this module is not testing us on c programming, but on how careful we are when we are doing the test. |
| 255. | The lecturers have been most encouraging in the way they present the course lectures. As for the method of assessment however, I believe there is much room for improvement. Firstly, the mid term test demanded extreme meticulousness and absolute knowledge of the compiler's ability, which is helpful to our programming if we do possess such knowledge. However, does that mean that not having such knowledge would mean we have no understanding of computing? Secondly, I believe many people are struggling with lab sessions. It is asking of us to speak in a new language almost immediately after we have gone through the lectures, and the stringent nature of labs may put off some people. Which isn't exactly the best way to introduce a new subject to many. |
| 256. | find it hard to write programs by hand since most of the time we do it in a com. Too stressful to complete practical exam in less than 2hrs. fun to have sucessfully programed; hard to find this fun enjoyable. |
| 257. | Even though the basics are taught and the students are expected to practice on their own, i feel there is too little time for those students who have not studied programming before to adapt to programming. Perhaps there can be more discussions on programming techniques and tricks which might help to accelerate the student's adaptations of the programming language. |
| 258. | The lectures were generally well-taught. There were insufficient discussion on the tutorial questions. Perhaps more time allocated for the discussion. |
| 259. | too much too fast |
| 260. | Many lab sessions which are good for practice. |
| 261. | I think should go through more examples during lectures to show how certain concepts are used in problem solving. |
| 262. | covered during A levels for some subject so was not too interesting but able to cope better with work as we adjusted from army life to uni life |
| 263. | Strength is that online learning is made possible as the lecturers are always available in the ivle forum to answer our doubts. |
| 264. | tutorial and lecture notes should be out earlier. pace whould be faster at the start and slower at the end. pointers should be teached before arrays which also be taught earlier. too much time spent on functions and all the loops. lab way too difficult |
| 265. | Work solutions not clear at times. |
| 266. | its interesting to learn how computer programs are written. post the corrections for all the printing errors in the textbook online. |
| 267. | Well, its better to give more different type of questions for computing so as to give more exposure to the different type of usage for it. |
| 268. | Too slow at the start. Its not a wise move. |
| 269. | The lecturers assume that we understand all the concepts that they are putting across, which is totally not the case. And most of the time, they do not care to explain further. Also the schedule is such that most of us do not have the time left for revision - by the time the lecturer finish his/her module, we are left with 1-2 weeks for revision... ridiculous. |
| 270. | Strength: (1)Interesting (2)Lectures are conducted at an approriate speed. (3)Notes are very clear and informative Weakness: (1)Answers to tutorial questions are only for a few specific questions, thus making it difficult to check through all solutions for those who make the effort to do the questions. Improvment:(1)Include the solutions for all the questions in tutorials. |
| 271. | excellent module but tutorial questions need to be scaled to same difficulty as exams |
| 272. | The change of lecturer to a new one during the mid course did have a negative effect on my understanding of the lecture |
| 273. | A good skill to acquire. |
| 274. | Things like structures, pointers which are more complexed should be taught earlier so that we could have more time to practice before the Practical Exam. Else it would be a good idea to push back the Practical idea further. |
| 275. | Strength: Programming expose us a totally new language based on logic. Weakness: Too much things to understand and too little time given to absorbed them. Possible Improvements: I must say that programming is afterall a new language to most of us, probably more time should be allowed for most to better absorb the materials taught and truely appreciate the language itself. But, since the time to complete a module is fixed, maybe what we can do is to focused on certain areas rather than trying to learn a lot without true understanding. Is it also possible that Mr Raymond be the lecturer for the later part of the semester instead? I feel that since the later part of the course is harder, it will benefit students if he is the one teaching. As I feel that he can generally teach better than other lecturers. |
| 276. | Weakness - Could link the programming to more interesting stuff other than hurricane, typhone or tsunami. Different variety of examples can be used to illustrate how to apply the different concept. |
| 277. | This module enhances my analytical skills and makes one more marketable. |
| 278. | Good lecturers. |
| 279. | Little help was provided for the lab practical. Much help from friends could result in plagiarism. Hence, leaving students with no programming background very helpless. |
| 280. | Bi-weekly labs have too little weightage, with respect to the time spent on the labs. |
| 281. | Lecturers and tutors did their best to explain the sometimes abstract concepts of programming to the students, making life easier for those who has no prior programming knowledge. I question the usefulness of the C langauge, as C++ and Java are more commonly used nowadays. |
| 282. | The way teaching is done for this module is very warped - some of the problems posed are so uniquely exclusive you literally need to work out how the lecturer(ie.Mr Raymond Tan) thinks and follow his thought process to solve the problems. A far cry from the way programming textbooks are written which make the process easier to learn and more fun as well. |
| 283. | The practical exam is too short for first timers to the C language to complete. Make it longer. |
| 284. | Weakness : Too much emphasis on syntax in MCQ papers. : Hard/Important modules were taught in a hurry (mostly towards the end of the semester) Strengths: We have good lecturers who make the subject interesting. |
| 285. | Too rushed at the back of the syllabus. |
| 286. | This is a great module which enchances my problem solving skills. The lab sessions were great as they allow me to apply whatever i have learnt into solving the questions. This is the module that gave me the most satisfaction this semester, not in terms of grades, but rather the knowledge attained throughout the course. |
| 287. | Lab questions tended to be abit vague sometimes; the explanation of the question wasn't clear enough (phrasing of the question wasn't done very well sometimes). |
| 288. | The questions for lab and some tutorials are usually quite difficult. And it can be a little heavy as i do not have any programming background. |
| 289. | Programming is useful in the future. |
| 290. | more interesting than other modules. |
| 291. | There should not be two separate lecturers for this module because both lecturers have different teaching styles and it affects our learning. |
| 292. | I find that the class participation for the tutorial is not very effective as most of the foreigners are very active in the class participation and ends up local tends to loss out. |
| 293. | weakness: 2nd half of the module should have more hands-on exanple during lecture. So the students are able to understand stuff like pointers, arrays more clearly. |
| 294. | The last lecture and tutorial should be conducted at least one and a half week before the practical exams so that we have sufficient time to prepare before the practical exams esp since the last few chapters are the toughest |
| 295. | too short a time frame for us to gain the necessary experience to tackle the standard of problems given.But might be easy for people who have taken programming before. |
| 296. | This is a difficult module for those with no computng background, it is clear that many of the overseas students have a good background in computing. It is clearly unfair for us to pit against them. Its the same reason why students from poly are not put into this module with us. It is said that there are students from past batches who did extremely well but have no background. I would like to highlight that this is probably the minority. Many of my local peers have difficulty trying to master the module in the short 3 months span. The lectures might be easy to understand but applying it in the questions is a different matter. It is also sad to see some of my peers losing hope in their engineering field or the electrical engine field, many thinking of changing their course of study just because of this CS module. There is a reason why people spend 17hrs on the lab questions. It must be noted too that it is difficult to spend as much time as we much wish to on practising coding as we have other modules to deal with. The maths and physics modules are not easy too and require their amount of attention but the overseas students have already done all the maths and physics in the countries. This done not account the fact that guys have to serve 2 and a half years of army, trying to play catch up is not an easy feat. The point I am trying to bring across is not that locals should not want foreign competition but rather fairer competition, I am sure if we were competiting with them after a sem or 2 of computing, we would be on better ground to compete. I am sure I am not the first or the last to point this out, but sadly I doubt anything would be done, yes we are in the top 10, thats probably the way we work our way up there. So what can be done? Just keep studying. Thats probably the strongest NUS culture. |
| 297. | I feel that there should be tutorials and lectures that are specifically schedule to teach us how to tackle exam questions. |
| 298. | lack of practice time for the students |
| 299. | The pace of the module is quite bad. Simple coding like 'printf' 'scanf' and loops should have been covered faster so that we have more time to study more complex ideas like pointers and arrays. The last few weeks we were literally rushing the slides. |
| 300. | i think think the lab lessons are difficult and the time span is too short. It would be much appreciated if the time for one lab session would be extended to 3 hours . |
| 301. | The module focuses more on the technical aspect of programming. As such, many students know how to program simple programs, but get stuck at complex ones, since they do not have sufficient lessons on the thinking process behind programming. Simple lessons on the different types of sorting and searching, as well as thinking in terms of linked lists, can help train students to think like a compiler instead of an language major who focuses more on syntax and semantics. |
| 302. | This module introduces to us the basics of programming which will aid us in future. As the topics nearing the end of the syllabus seemed rushed, i suggest that the topics taught be equally distributed lecture periods. |
| 303. | Strength: Help us to make use of our logic thinkings to solve the questions using programming methods. Makes us use our brains more and not taking the programs for granted. Weakness: Slower students tend not to follow the pace of the course. Maybe students should undergo a introductory course on programming before taking this module. |
| 304. | Some students like myself are using the textbook, so it would be a good thing if we could be told which parts if any are not being tested. Besides this, the module was very well planned and the admin was also good. |
| 305. | I feel that the module is very complex at the end as the skills we learnt we interlinked and it gets quite messed up. Should teach problem solving more instead of skills. |
| 306. | Not enough lab time to practice, suggest MORE labs. |
| 307. | i)Lack of time for students to get used to programming for the first time ii)Detailed presentations for teachings iii)Lack of animations to show the exact happenings in memories and functions of programming iv) More examples to aid students in programming v) More time for practical work(e.g. some time for students to formulate own algorithms before starting work) vi) Teach on methods of debugging, sequential coding |
| 308. | General i find the module really interesting and i really got the passion to find out more, how to program etc. It maybe due to my tutor Henry Chia who really did a good job in explaining the details to me. However the module is still relatively difficult in the sense that i always got tricked by the MCQ so i still not very confident that i can do well. |
| 309. | The learning curve for this module is slightly steep, especially for students without programming background. maybe it would be good to have just one lecturer instead of two. |
| 310. | this module is really not easy to learn. Despite doing all the tutorial questions, I still have difficulties with programming questions, especially for lab4. |
| 311. | The topics covered are extensive but interesting. However the labs were always very tough thus discouraging. |
| 312. | The module was difficult, but from what I was told, it was much difficut before. So I have no complaints. However, I felt that the last few topics were taught very late and we had no time to familiarise ourselves with them. After all, programming is about getting familiarised with the different ways of doing things. Its true that I was supposed to have practised myself at home, but with all the other modules doing the same last minute rushing, I found it quite hard to cope. The only consolation I get is that the practical exams did not really include the last few topics. |
| 313. | Strengths: Interesting, comprehensive; Weakness: Lack of exposure to more complex questions before Lab sessions and PE. |
| 314. | I felt that the topics were taught towards the end a bit to rush such that there wasnt time to actually really understand the topics. There were lots of emphasis on the starting topics which was good as it help me to understand better however as there was quite a bit to cover, towards the end i felt it was rather fast. |
| 315. | This module introduces us to programming and provides us a basic understanding of programming. We learn how to program simple programs that might be of use in our course of study. However, as the majority of the students are new towards programming, it might take quite some time for us to grasp the fundamentals. The module was taught slowly and steadily for the first few lectures. However, as the contents of the module got harder to understand, the lecture pace got faster and faster and was quite rushed to the end of the semester when the exams are approaching. It will be better if they go slower and give us more examples with regards to topics like 2D arrays, pointers and etc.. |
| 316. | provide solutions for all the tutorial questions |
| 317. | it provides rigorous training,sharpens my thinking skills and enchances my creativity. |
| 318. | this module is on an unfamiliar topic, so it is interesting to learn whole new concepts. however, one needs lots more practise than other modules, i feel, to score. having weekly lab sessions could help, and not testing for plagiarism could encourage dicussion among those who truly need help and are not just aiming to copy off others. |
| 319. | The module is designed for people who are already good in C programming and doesn't give amateurs like me enough time to gain adequate skills to perform the assignments or do well in the exam. |
| 320. | This module exploits the strengths of a powerful language like C.The standard is very high. Those with little or no programming background cannot expect to do well in this module. So, the syllabus should be such that even novices start on par with the programmers |
| 321. | The module wonderfully is excellently maneuvered to start off from the basics of C, to move on gradually and effectively to the higher and complex aspects of the language. One of the main strength of the module is the excellent team of tutors and lecturers. It would however do more good to the students if there were more lab sessions and emphasis was on gradually enhancing the skills of the students, rather than taking 'giantish' steps towards developing programming skills in the student. |
| 322. | It was a splendid module... I only want to quote about my practical exam... there must have been a mock P E, because I just messed it up on that day and dint submit my final output i got ! I dont think 1 45 min is enough for most people as it reduces to 1 30 min on the day ! So if you can improve on the timing and give the students may be 15 min more , it would be great ! |
| 323. | should focus more on students who have no basic knowledge of programming instead rushing through the topic.spend more time on explaining the topic clearly |
| 324. | no comment |
| 325. | based on MCQ: Even though exams are open-book, questions are too difficult. Questions are tailored in such a way that only really really observant candidates would spot mistakes, although most students get the answers correct by chance. Humans are not computers, we shouldn't be expected to be one. |
| 326. | This module is quite tough so i think it should have more practice on it like having more example on programming. |
| 327. | i think one semester is not enough for the students to understand all the C programing concepts |
| 328. | the main objective of the module is to expose the students to the world of programming which is 100%correct. but the way they have done about doesnt serve the purpose. there are many people like me in the university who havent done programming before. so for them to catch up with the pace is veery very tough. why not there be a basic prereqisite module for this module , like the CRITICAL THINKING AND WRITING. this would immensely boost our self confidence. |
| 329. | I think it is the most attractive module during this semester. |
| 330. | The chapter about the POINTER quite confusing and I found that Pointer is quite useless. |
| 331. | The amount of material learnt is too much for such a short duration. As compared to other subjects, CS1101C is something completely new for me. So, more time was needed to understand the subject. |
| 332. | More programmes examples |
| 333. | A qualification Exam like QET should be kept for this Module. Its very hard to do any subject when one doesnt have knowledge about it all.:(:( |
| 334. | Very few examples used to give us more understanding. |
| 335. | This course would be useful for the Engineering syllubus. However, I feel that we should learn more updated programming languages like Java. |
| 336. | The exam format of this module seems to be testing if the students know how to compile a program without a compiler. Maybe the exam format should change to a fully computerized exam such that it really test the student's ability in programming |
| 337. | more sample qns |
| 338. | Please train us to write better code and not be a better compile machine and more time should be alloacted for practical since it is not the quantity but the quality that matters. |
| 339. | I think that the course on overall may be a bit too much for some of the first years, primarily cause many of them have little to no prior knowledge of programming at all. On the contray, for those who did take programming find it a breeze, so there are two ends of the spectrum. Also, I find that while the lectures and tutorials are result oriented, in the sense that the idea instilled in us is just to get the desired output, the test and exams tests us on the minute details. I suggest that the course in future be more focus on the minor details that are assessed ao that those less attuned to programming can possibly fare better. |
| 340. | Have easier practical labs/exams. |
| 341. | Lecturer Raymond Tan has successfully introduced programming in a very friendly way to all newbie programmers. His usage of sunfire during lectures is very helpful and useful in making us understand certain topics better. Thus it would be beter if lecturers are able to show students the way to programme using the sunfire rather than jus plain powerpoint slides. |
| 342. | Interesting module. Get to know lots of new things. Questions for labs, tests and exams and all quite related to the questions we do for tutorials. Therefore, we are sometimes shock to see such questions. Have more tutorial questions that are more related to the types in exams or tests rather than those from textbook. |
| 343. | The different sessions for practical exams may be unfair to students, as some of the sessions consist of question very similar to last year paper, while other sessions are very different. I would say it is unfair as most students would do much better if they were lucky enough to fall in that particular sessions. In addition, i find that most of the skills that are needed for partical exam were not taught to us. However, it has been a interesting topic to learn especially for someone who doen'nt have programming background. |
| 344. | none |
| 345. | The pace of the lectures are sometimes going too fast. |
| 346. | This module is interesting but it's hard to understand as it is a new language. |
| 347. | Shd teach at a slower pace and shd have fixed consultation sessions for student. |
| 348. | If more examples of programs were being shown understanding might be better. |
| 349. | The lecturer for the second half of the module seem to be talking to himself during lecture. He do not seem as experienced at Mr Raymond Tan whose lecture is more interesting as he illustrates examples as compared to the other lecturer who only read according to the slides. |
| 350. | AS I AM NEW TO THIS SYSTEM I FIND ALL THE MODULES DIFFICULT. |
| 351. | Have done programming before so not too bad for me but tough for students who have never done it before. The module should be worth more MCs. |