Previously on CS399J...
After ten years, how did we do?
- What do you wish you had known before taking this
What is the most important thing you have learned in
- I wish I'd known a bit more about jar/war files, command line parsing, web containers, client/server specifics, REST services, GWT and more about integrating the tools necessary to use some of these features on common IDEs. Lots of cryptic error messages that came up really made it difficult to make consistent progress on the last projects.
- There was no surprise.
- *how to use an IDE better. (vi could've worked well if i was more prepared i suppose- with all the maven/jetty/gwt terminal stuff)
*i wish i know how to use maven properly before class.
*i wish i had SOME experience with networking with java (jetty stuff)
*that there were no outlets in the classroom.
- I wish I had been more proficient using Eclipse (I'm better now).
Even more, I wish I were a Maven "god". There is so much to learn about that powerful tool.
- More about maven.
- I took most if not all of the CS required course, so not sure what to list. However, an advice to future students would be CS300 (actual OOP program from analyze user requirements to working OOP program), or CS321 & 322 (Compiler where Professor Mark Jones have us implment a Mini Java Compilier (MJC)).
- It certainly would have been easier to ramp up if I had done more programming in the previous 6 months, or if I knew maven beforehand.
I can't complain, though--I got settled in after the first 2 weeks, and I've learned a lot.
- Maven, subversion (or other CMS), more comfortable with my IDE (Eclipse, then NetBeans)
- A little more about the IDEs available. Otherwise, nothing.
- I wish I had had previous experience with the IDE and especially Maven, as I wasted a lot of time figuring out the tools before being able to start any real "work."
- I wish we had access to more resources.
- Better understand about Java, and know more about Eclipse, Maven, etc.
- I feel that I was relatively well prepared for this course, and nothing comes to mind immediately.
- I wish I had known more about Rich Internet Applications with Java. Having more background with Maven and JUnit would also be helpful. There were several things that were knew to me and it seemed to take twice as long as I hoped to be able to apply these technologies.
If you could give one piece of advice to someone taking this
course in the future, what would it be?
What made you stay in this course?
- I have learned much from the course but some of the main things include:
1) real world expectations of programmers/developers
2) the importance of testing everything as you develop
3) how to use great build tools like Maven/Ant with IDE's like Eclipse to speed up the development process
4) how to implement client/server software at a basic level and work with Tomcat/Jetty containers
5) I was also exposed to many other types of frameworks commonly used in industry through doing much research on each project
There are many other things that I learned but these are among the top of my list.
- Maven, and GWT
- There are so many- documenting code, more efficient coding, i learned that class is nothing like the real world. and procrastinating is like shooting yourself in the leg. and if you don't know something, you're not the only one.
save, save, save, test, test, test.
I will never use eclipse.
- Beyond greatly improving my Java skills, I have learned a huge amount about using the many tools that enable effective Java programming and development.
- The JUnit framework and how to document your code well. JUnit is a life saver.
- All the neccessary tools and their interrelationship to build a real world program using Java. Not so much of Maven, but Eclipse IDE and Google Web Toolkit.
- That is a tough question. I would say this is divided between learning about REST / HTTP / servlets and learning about Maven. I never had a formal introduction to REST prior to this class, so learning about it made me more confident as a web developer. Servlets are no longer so mysterious, nor are web.xml files.
Maven is important, because I like that it handles your project without too much abstraction. When I create a web project using an IDE, I have no idea where all the different files come from--which are IDE dependent, and which are part of the core project?? I especially hate Visual Studio for this reason. With Maven, you can easily customize the project using your pom.xml file, and I find it helps me to learn about the structure of various projects i.e. webapps and servlets.
- How to implement web services (either REST-ful or via GWT)
- Using maven and junit. It was probably the first section that was discussed that I was unfamiliar with. Both of them combined make developing more streamlined.
- Working with the servlets and GWT. I'm still trying to figure out GWT, but I can see how this is a great tool for developing Internet-based applications.
- The practice programming was most important.
- REST, and GWT.
Also learn a lot about JAVA which is a popular programming language.
- Maven, JUnit, and how to put together a relatively robust development environment are the most broadly useful things I learned in this class.
- I have learned how important testing can be to your development. It saves so much time if you write the tests before writing your code. It also help me understand why I was doing what I was doing. Also I am so grateful to have spent some time with Google Guice and GWT. There are amazing and will help me so much with the work I am doing.
Want to hear what other people had to say? There are lots more comments from previous