P1 feedback about 45 responses 3 1HoursAlone: 7 1HoursAlone: 1 or less hours 5 1HoursAlone: 2 hours 6 1HoursAlone: 3 hours 6 1HoursAlone: 4 hours 8 1HoursAlone: 5 hours 5 1HoursAlone: 6 hours 2 1HoursAlone: 7 hours 2 1HoursAlone: 8 hours 1 1HoursAlone: 10 hours 22 1HoursWithPartner: 2 1HoursWithPartner: 1 or less hours 6 1HoursWithPartner: 2 hours 4 1HoursWithPartner: 3 hours 7 1HoursWithPartner: 4 hours 1 1HoursWithPartner: 5 hours 2 1HoursWithPartner: 6 hours 1 1HoursWithPartner: 7 hours 1 2LearnCoursePolicies: 1) very bad 5 2LearnCoursePolicies: 2) bad 16 2LearnCoursePolicies: 3) ok 15 2LearnCoursePolicies: 4) good 8 2LearnCoursePolicies: 5) very good 3 3LearnCourseWebsite: 2) bad 12 3LearnCourseWebsite: 3) ok 19 3LearnCourseWebsite: 4) good 11 3LearnCourseWebsite: 5) very good 1 4LearnCourseNewsgroup: 1) very bad 6 4LearnCourseNewsgroup: 2) bad 10 4LearnCourseNewsgroup: 3) ok 14 4LearnCourseNewsgroup: 4) good 14 4LearnCourseNewsgroup: 5) very good 2 5LearnRunMatlab: 1) very bad 6 5LearnRunMatlab: 2) bad 18 5LearnRunMatlab: 3) ok 10 5LearnRunMatlab: 4) good 9 5LearnRunMatlab: 5) very good 4 6LearnRunCodeWarrior: 1) very bad 7 6LearnRunCodeWarrior: 2) bad 21 6LearnRunCodeWarrior: 3) ok 11 6LearnRunCodeWarrior: 4) good 2 6LearnRunCodeWarrior: 5) very good 2 8Overall: 1) very bad 3 8Overall: 2) bad 19 8Overall: 3) ok 18 8Overall: 4) good 3 8Overall: 5) very good ---- q> Even though it was tedious to answer all the questions, I think it q> was very helpful. I still feel a little uncomfortable with Matlab q> and Java, but I'm sure I'll feel more at ease with time. i'm not entirely happy with the course website, but it is organized reasonably well and has lots of relevant information. it seems like the project overall did a good job of getting people familiar with the course website. ---- q> It is still confusing how to access Java files ---- q> The number of questions about the course was a little q> excessive. For example, asking what email address a certain person q> prefers is trivial and time-wasting for the purposes of the q> project. ---- q> It was a decent setup for a first project but next time cut back on q> the questions in Part A....40 is a whole lot, and last semester q> they only had like 10. It took me a very long time and was quite q> tedious. The rest was pretty good, but I couldn't make it to q> either demo time so had to struggle to get the Codewarrior stuff to q> work. Perhaps next time offer more demos, or do it in section. 10 was too few last semester, which is why we had more this semester. ---- q> I thought this project was very useful because I became more q> familiar with Matlab and Java and without this project, I probably q> would have never learned how to use a newsgroup or any of the q> details about this course that are on the course website. ---- q> I thought the Matlab program was helpful in letting us learn how to q> run scripts in Matlab and using "addpath." However, for q> Codewarrior, I thought that even after the software demo, I was q> still confused about running the project and program files. The q> hardest part for me was actaully installing Codewarrior on my q> computer, especially the CUCS Application files and the Sun q> Microsystems files. I think it should be emphasized at the demo q> that the Sun Microsystems files also need to be installed to run q> Codewarrior. ---- q> I really learned a lot doing this project, yet I think that Part 1 q> was a little too exhaustive, as it actually took the longest to do q> and was really just a matter of clicking around until I found the q> answer. I do see the point in including this part, yet I think it q> could have been greatly condensed. ---- q> There was only some minor editing of the programs we were assigned, q> and not as much learning about how to write progams. ---- q> The questions had little/nothing to do with the actual class. ---- q> This assignment was very time consuming and I was confused by it q> because of the vague directions. I've never used Matlab or q> CodeWarrior before and the tasks we had to do in the homework were q> not yet discussed in class. I also found the course website very q> confusing to use since thigns are all over the place and there is q> so much information on it that it is conjested. ---- q> code warrior seemed confusing, that's still sketchy to me when we get to java, we'll give you more help on using codewarrior. ---- q> I found myself lost when at the computer - although I took notes q> during the demo lecture, it was too fast pace - and since it wasnt q> hands on - wasnt helpful. I beleieve that the only people who q> actually were able to get on successfully - were those who had q> someone show them. It would have been very helpful if during one q> of our first section meetings we had met in the lab to have some q> guidance as to how to run matlab and java. i foung it very q> frustrating! ---- q> I don't think that it oriented us very well with the two programs. ---- q> The software demo was the most informative part so far. The part I q> questions just seemed like busy work, and took the most time. ---- q> Most of the questions in part A seemed like a waste of time, but I q> thoroughly enjoyed the other parts--they introduced the software q> and the "feel" of programming without concepts we have yet to q> learn. ---- q> very time consuming, but informative nonetheless ---- q> Pain in the behind. Answers to some of the first questions weren't q> even on the spring page, had to go to the fall page to find them. q> [censored] ? i'd be interested in knowing which questions. ---- q> It was a good project, since it covered a variety of topics and q> gave a general idea as to how the class was going to be. ---- q> I havne't understood much in lecture, so doing this, and getting a q> look at MATLAB and Java helped bring a few things together. I'm q> starting to understand little by little. ---- q> the project was rather easy, but it required a long time to work on q> it, especially the questions, but it was very useful to understand q> how the class is run and to know where to find help and thus avoid q> any bad surprise later. ---- q> This project was very useful, but part 1 had way too many questions q> and much of it could have been avoided without losing any of the q> usefulness of the project. Especially the three redundant q> questions about "are late assignments accepted" etc. ---- q> Most of the project was boring and kind of menial. Sure, it forced q> us to look around the website and check the newsgroups, but some of q> us would have appreciated it if there had been fewer questions as q> it took a lot of time to surf around and find the answers. q> Otherwise the project was OK. The birthday problem especially was q> rather thought-provoking. ---- q> Good intro project! ---- q> More background info might be helpful...my section didn't cover any q> material the first week due to overcrowding so I felt a little in q> the dark. I eventually figured things out but I felt they were a q> little harder than they should have been. ---- q> The demo was necessary in order to understand what we needed to do q> for the project. For example how to use the actual programs and q> how to edit them. I think that maybe if an example of how to use q> the programs was given in class it would have been easier.... maybe q> for example if a handout on how to start a new project in each was q> given out so that we could have a hard copy on how to get started q> with a project. ---- q> The programming parts were actually kinda easy...the hard part for q> me was to answer all those 40 q's...and the algorithm part My q> partner and I didn't really have an idea of how to do the algorithm q> part until we asked someone who took CS100M last year. I think the q> instruction wasn't clear enough.