Previously on CS399J...

Another huge class. And since this was "advanced" Java we learned about GUI programming. Let's see what the students thought about it...

1. What do you wish you had known before taking this course?
• I wish I had known more about basic java which could have helped me digest the material and the topics covered quicker and easier. Because I like to be creative and go beyond the limitations of the class. So hopefully this coming break, I will definitely be playing with java tools because it is really a fun language to learn.
• I wish I had more experience with programing before taking this class. Especially I wished I knew about basic Java before this.
• I wish that I had better experience in C++ since I just finished my 162 and this class was the hardest class I did ever took.
• I wish I had some knowledge about java, the basic stuff.
• Before taking this course, I wish I had been familiar with the Java API. OOP is a really nice concept, but being used to C++, I had a hard time with Java because all we do is reused code. I am used to reused code but all those convention that holds Java and structures it I wish I had known them ahead of time.
• How to use Eclipse with CVS
• Better understanding of UNIX
• I wanted to know about networking and GUI programming in Java, and improce Java language skill.
• How to download all Dave's classes so I can compile on my own box instead of working remotely or at the FAB.
• Nothing more than what I know
• I didn't know that there were 2 sections of the class. I signed up for the "self support" sections and had to do battle with registration department to get my $500 back.
• Nothing. Dave did a great job of providing all the information we needed to be successful.
• Nothing, whenever I wish to know about something, I go read about it.
• Nothing
• Nothing. I feel like this course started with the basics for Java and progressed at a reasonable pace.
• I don't wish to know anything before -- but I've done a lot and know a lot by now.
• That I could have taken it before CS300. So I would have been able to do that in Java instead of C++.
• Possibly a little more expose to object oriented programming in general. I really wish a textbook would have been required. I know, I can do it on my own, but I guess I just do well with more structures. The lectures/slides are good, though.
• Learn all the Java standard API, and some overview of the JFC.
• That this was the only elective I needed (thought I needed two). Other than that, nothing.
• To know more about Java programming. Create GUI.
• The amount of work involved, projects, assignments, final okay, but why two extra group assignments?
• I would have liked to know Ant a little better.
• I had already learned about inheritance and classes i CS202 (C++ programming). I think it would have been more difficult without that information as background.
• I wish I have knon more applets and XML. I want to make Java game.
• Java. :) Actually, I learned a lot about the different Java resources online throughout the course. Would have been nice if I had those at my disposal when the class started.
• How to program well. The course is perfect for someone with experience in another language. Trying to learn Java syntax and programming methods is a lot to handle.
• More experisnce with either the basics of Java or more experisnce with object oriented programming.
• Not much. Maybe X Windows connectivity so I could test my GUI on UNIX.
• How Java related to web program
• I wish I'd known more about executing Java on the command line.
• How to create a GUI
• The characteristics/special language features of Java language. The reasons Java can run across platform. The reasons Java is getting popular nowadays.
• More about setting up and using cygwin.
• I've learned C++ which was only programming language in my CS courses. So I always wanted to learn some graphic features that I can play with 'em. Also, how to make efficient program.
• ActionListener. Network.

2. What is the most important thing you have learned in CS399J?
• The most important think I have learned is CS399J is the GUI stuff. In all of my other computer science classes, I always wondered how I could convert my codes and programs to something that could be understood by others who have no knowledge about programming and coding. I have done some really interesting projects in my other classes and know I will try to implement them and create a graphic interface for them.
• I learned about how to program in Java
• Java programming and how to catch to the class in better way.
• How to code using java language which is a little bit different than other languages.
• The most important thing I have learned in CS399J is testing. I knew the importance of OOP and am pretty familiar with it. But testing never had such a huge impact on my coding other than in this class. Also I learned the impotance of writing clean and correct code so that people can reuse them. Mine wasnˇ¦t corrent and it penalized me for the rest of the course since we had to reuse the code. It can be pretty frustrating.
• MVC and how to use Ant
• Object oriented programming with Java
• The most importand thing I've learned was object oriented properties of Java and the ability to make code modular and wasy to debug and understand
• Learning to make GUISs and using javadocs; using Java's prebuilt classes, APIs
• Java and Javadocs
• Programming with extensibility in mind, especially how Java faclitates that. (Program to the interface)
• The most importand reference in a language like Java is the API reference -- knowing the tools is almost more importand than the language syntax.
• Java! More specifically the differences between Java and .NET. Javadocs are awesome and C# has no real implementation of MVC.
• Probably it being a good example of developement practices, as well as a good semi-in-depth understanding of the various Java technologies.
• GUI programming. Most of the non-GUI stuff I already know.
• Object oriented programming style
• I have a much etter grasp of designing reusable, portable code, ineritance (which I only vaguely understood before) and polymorphism.
• GUI programming, packets
• Checking error in your projects as much as you could
• Thought the GUI stuff was really good
• I learned that Java is powerful and very "learnable" if you put time into it.
• To know what is available in Java API, and how to use them.
• Swing
• GUI, Swing. I love them.
• GUI programming with Java, AWT/Swing
• Use of the javadocs came in handy. I can pretty much figure out anything from the javadocs now.
• How to research and use Sun's Javadocs. Very helpful.
• I elarn how to program in Java and what different between Java and C++. I also learn Swing and GUI. I like those stuff.
• Object oriented program design. I'm a big fan of it now.
• How to find a functionality in an existing class using the Javadocs and plugging it into a program. Design patterns runs second.
• Java provides a rich set of tools for modeling computing solutions.
• MVC
• (Abstract class) object oriented concepts. GUI.
• Swing! I now want to pursue a career in GUI design.
• Everything! This class has vastly improved my knowledge of Java, from the rudamentary to the advanced topics.
• Understand the Java language and how to program with it.
• New concepts of OOP (garbage collection), core API and useful tool package (JUnit).
• The important of clearly defined requirements.
• Java! GUI. I think writing a basic GUI is a pretty fundamental skill for a Computer Scientist to have. Be able to present and visualize data is very important. Compared to C++, Java Rocks!
• After project 1a assignment I'ce got low grade of my project so everytime I had to fix my program. Then I realized what exactly my probem was. I think that I learned how to figure the concept out.
• Package. Hierarchy.

3. If you could give one piece of advice to someone taking this course in the future, what would it be?
• I would encourage him/her to write a POA before starting any program because it really helps and if possible have the instructor or somebody else look at the POA and evaluate its efficiency give suggestions to improve it because I really found it helpful to write a POA that organizes your work and makes you think than code rather than using the method of "trial and error".
• Read the Head first Java book before taking this class If you have no experience with the Java programing. At the beginning of the class I realized I need some extra help with Java then I found this book at the library. while I was doing my homework and studies for the class, I did study this book as well.
• It is not taking advance java class before taking the basic java also it is better to have good experience in C++.
• He should have at least some idea of what java is about.
• If I could give one piece of advice it will be to really understand your goal and write a Plan of attack and stick to it. Of course understand how to search the API is important too. Also you are competing with people from the Industry and Senior or people who have been exposed to Java so it can be pretty frustrating as they know more than you do.
• Start thinking about project design first and as early as possible
• Start early on the projects
• Read the slides and plan before coding. Start thinking and researching early to get the best project solution
• If you really study the lecture notes Dave provides, most/all your questions will be answered to solve (finish) assignments (so you don't need to bother Dave)
• Don't hestitate
• Pay special attention to the aptterns/practices that you see/learn. Study Dave's code for labs/quizzes/and good practice. He does things in his examples you probably would not think of on your own.
• Read Dave's sample code on the web site. Make a link/bookmark to the API docs -- you will use them a lot.
• Plan ahead, there is a lot of programming in thie calss. Make sure it will fit into your schedule.
• Get at least a basic undertanding of Java before you go into the class. It will allow you to learn about the finer (more valuable) points of Java instead of fighting to learn the basics.
• Show up to class
• Study hard
• Pay close attention to that wacky Dave -- you'll miss is quirky humor if you don't
• Study a little Java before taking this course
• Be prepared -- there will be a lot of time required to do the projects
• Drink plenty of coffee before class so you can keep up with Dave talking.
• Keep up with the projects. Make sure you will have time for the class before registering.
• More lecture on AWT and Swing, and shorten the lecture on the language.
• Pay attention to the basics, for they shall serve thee well.
• The best elective course -- enjoy the project -- they are fun.
• Be prepared for more difficult sasignments later on in the course.
• Use the javadocs and make sure to comment your code. Start project early. Take the time to learn XML.
• Start projects early.
• Do the program early. The program is easy. But it take time. The last program is always the hardest. Read some Java book to undertand more about the subject.
• Don't leave projects until the last minue. don't forget to laugh at Dave's jokes.
• Start the assignments early. Right after lecture would be good.
• Ask questions.
• Learn and use Java before taking this class (it is advanced) or you must be comfortable with object-oriented programming concepts in order to survive this class.
• Good class, very useful program, and fun
• Stay on top of the assignments -- do them ahead of time and you will thank yourself! This gives you time to tinker, which you'll want to do -- especially with Swing.
• Ask questions about the assignments lest you lose points.
• Don't take with compiler or OS class because it's time consuming.
• If the one has already know OOP characteristics, just go ahead and enjoy it!
• Ask questions to clearly define what is required for the projects.
• Java Rocks -- forget C++.
• I can say that "Check Dave's website and understand his Java work!" Ah...use mailing list.
• Start early. Good design document.

4. What made you stay in this course?
• More than one reason: 1) The help and feedback we used to get from our instructor via emails. 2) The desire to learn GUI. 3) Because we're required to take an uper division CS class and java was the most intersting one among others.
• This course even thought wasn't easy for me but it was interesting and useful. I like the challenge, I thought I will stay to try and to learn more.
• My teacher is really understandable person, and I strongly want to learn java programming language.
• The instructor made me stay in this course because he is very nice and very understandable (clearly explains the material).
• I stayed in this course because I understand the emergence of Java in software application. I really C/C++ but it is mostly used only in firmware. I would like to become a software programmer in the future.
• I enjoyed the material and the class
• Java is run. Enjoyed the lectures and the projects.
• Interesting material, and friendly class environment.
• Everything...honestly. I learned a lot and it was FUN! ASsignments were challenging but not overbearing. I like the one-night-a-week course.
• Great instructor, helpful slides and examples, GUI, Java
• Quality lectures/quality lab assignments
• I really wanted experience with Java because of its prevalence in industry. The level (conceptual) of the lectures was appropriate for my level of programming experience.
• Good teacher, good topic, and I need the credits.
• Excellent instruction and subject matter.
• I want to graduate someday
• Why would I leave?
• I like what I was learning
• I needed it.
• The projects are interesting, and the lectures are simple and clear.
• Best programming class I ever had. Love Java. Thought the assignments were well thought-out, challenging and very useful.
• I really wanted to just tough it out.
• I want to know the advantage of the Java technology.
• I liked it
• The project is very fun to work, although it's time consuming.
• Counts as an elective
• I enjoyed the assignments and the lectures.
• Great class. Lots of new material. Fun projects.
• The reason is Java is fun and does make a lot of cool website. I want to make those website for my boss.
• I was interested in the subject matter. I needed the credits. I had a lot of quick, positive feedback on how I was doing.
• I want to be able to write programs to analyze data. Learning more about Java I felt it was in many ways an easy to use language. For example, garbage collection and memory issues.
• I was learning a lot of interesting material.
• Lots of things. I never wanted to leave. It was taught well by an engaging, attentative, and knowledgeable professional. The subject matter added to my prior experience with Java, GUI design, and OOP.
• I want to know Java as much as I can
• I liked everything about it. Java is a great language and the assignments were useful.
• It was either this or join a violence gang.
• I think you are a great professor. The lecture and assignment perfect suitable for this course. The material and examples very clear for me when I read through and able to find answer when I'm doing assignment.
• I intended to see more advanced techniques of using Java to write program.
• I'm a sucker! No really, I enjoyed learning about Java. I liked the lectures, I liked the projects.
• I paid $550 tuition -- do not want to lose it! Was an interesting class and an interesting subject. Learning Java is key to budding Computer Scientists.
• Instructor! :)
• I could learn about Java from bottom to top.


Still not convinced? There are plenty more comments.