Previously on CS410J...
When I taught CS410J in the fall I asked my students the following
questions on the last day of class (after plying them with pizza -- a
little trick I learned from Doug Comer).
- What do you wish you had known before taking this course?
What is the most import thing you have learned in CS410J?
- Object-oriented concepts. I still have to think about how
objects interact, etc.
- More about Solaris, UNIX...
- How to write Java applications
- I think [a] little bit more knowledge about OOPs might have
helped understanding quickly.
- More UNIX experience, or a crash course in UNIX (classpaths,
jar files, etc.)
- That the 1st program was going to be so damned hard.
That you would go very fast.
- Directory structure for compiling/packaging.
- More about networking, GUI and threads
- A little OOP, I had a hard time starting but its been more or
less fine ever since.
- That I shouldn't buy the book.
- How about oriented language works.
- Some basic Java first.
- How the Java compiler handles files, directories, class paths,
packages, and such because that was the hardest thing to
- A little more about the UNIX OS and a better understanding of
- I would have like to have been more familiar with OOP and how
Java implements it (implements and extends) mainly C# (just
joking) [Don't get me started on C#!]
- More object oriented programming knowledge
- Stronger Object oriented skills
If you could give one piece of advice to someone taking this
course in the future, what would it be?
- How easily Java code can be to write. Once one is acclimated,
with stong type checking and explicit compiler errors it is really
easy to prototype and test applications (no more pointer
- How to compile and run Java programs. How to look up stuff in
the Java docs. A better appreciation of object-orientation.
- That OOP in Java kicks hiney [sic] against socket programming
with pointers! Garbage collection is cool.
- I gain confidence in programming
- Object programming make program simpler
- I have learned how object oriented programming works and
- That Java has some excellent features/advantages and that it
certainly has a good future.
- I thought the team work projects were the most educational.
Too often we all operate in out little boxes and don't get out.
Speaking with others about topics that are cool - like Java were very
good. It opened my eyes and ears. The assignment were stiff and
challenging but they taught me Java the most.
- Concpets of OOP and experience in OOP and building
- There really wasn't one things -- I'm just glad I got
through review of the Java basics...
- The manner in which Java is implemented: standard class
library, compatability problems, no good development tools for UNIX,
global file structure for classes
- OOP, a XML API
- Using Abstract Classes to set up the frame work. Setting up my
own Exception class for reporting errors.. ParserException to
standardize Exception reporting. Better understanding of GUI
- As I haven't done any programming in Java. Everything is new
and important to me. I especially like GUI and socket programming.
(Project 5 was fun to work on.)
- Networking and threads
- The whole reason I took this class was so I could put a front
end on my programs. So, the GUI stuff.
- Swing was cool! Wish I had more time to do the last
- The basics, syntax rules (like not pass by ref), in the
- Basic Java functionality. Java programming style.
What made you stay in this course?
- Learn how to compile and set up simple little Java programs
before you start any projects
- Work hard at the beginning!
- Get the project done right! Start early.
- Don't be fooled by Dave's willingness to give you extra time --
finish your projects on time!
- Have persistence, patience, and be self-motivated
- Get all the details about the requirement of the project.
Don't assume anything. Do exactly whatever is specified.
- Stay on top of it and start the work early.
- Take it from Dave.
- Be ready for a lot of work, and have intimate C++
knowledge. ["I'm only going to say this once. I did not
have programmatic relations with that language, C++."]
- Know the basics about Java and the Colelctions classes. Know
something about networking and threads.
- Be sure you meet the following requirements: Understand OOD,
Unix, Data structures. This is a SENIOR level class.
- Don't wast time getting started and familiarize yourself with
the tools available, i.e. "Java docs"
- Buy a Java Refrence book and Programming Book in the areas
you're intrested in. Java Docs are not always enough.
- Make sure you have plenty of time!!! I spend about 20 hours of
coding for 1 day of class!
- Make sure you have lots of time for the projects. Interact
with your peers.
- Read the book closely to understand the language. Tell Dave to
- Although you learn a lot, there is a lt of work and time you
will need to put into this course.
- Know some Java
- Learning new things and challenge to new tasks.
- Java is interesting and the exercise in class are
- You like what you're doing -- you like to teach -- you use your
hands to explain things. The projects were way hard -- especially at
first -- not boring.
- I like challenges.
- How much I was learning.
- I found programming Java fun (believe it or not) [I believe
- I wanted to learn more about java --> RMI, networking, threads
(Didn't get to RMI, but nice try)
- I like Programming in Java. (Yeah, I'm a DORK!) I figure, if
I stick to it and show that I am trying hard to make my programs work,
I'll get at least a "C" so that I don't have to retake this
- Herr Prof. Whitlock! Really, you've developed an excellent
rapport with the class, and always kept lectures worth
- Needed upper division credit in CS.
- True Grit. Seriously, I enjoyed learning the language and I
got 12 pts on the first program. [That's 12 out of 12.]
- I've never quit anything in my life. The first project was
challengin but I am paying PSU to learn, not coast.
- In spite you... nah ..just kidding. I like Java and have
pretty good instincts with it. I lacked the formal instruction and
smack down to do it correctly. and I'm Irish and we don't give up or
leave the bar without a fight. :)
- Lecture was more interesting than my other classes, wanted to
- All the Fun.
- I enjoyed it. I wanted to learn the material. I paid for the
course. It was easy. Well till the end :|
- I enjoyed the challenge and like learning Java, and I need the
credits to graduate.
- I enjoyed the material. I really learned a lot out of the
course and Dave is an excellent instructor.
- Determination to learn Java. Started developing interest after
something (earlier project) started waning.
One thing that I like about my students is that they're always more
than happy to give me feedback about my teaching. Sometimes they use
more than one finger. Based on my experiences with this class I've
decided to spend a little more time at the beginning on the language
aspects of Java, object oriented programming, and compilation.
Last modified: Fri Dec 1 15:43:40 PST 2000