I'm curious what fundamental java knowledge is most used on projects. I'd appreciate a list of 5 to 10 things that java programmers find they use most often and hence must have an intuitive command of their usage. i.e. Casting, string manipulation, i/o, file writing/retreiving etc..
hi michael hum.... I think depend on which situation. Which type of the project you need to do? Such as information system. If you need to do through web base,some extra knowledge you need to know. Using JSP J2EE standard,Tag library,Java Beans..etc Common knowledge of Java include String manipulation,inheritance,method overriding,overloaded method,using interface,Exception,iteration..etc Hope this help
Joined: Oct 06, 2000
I had a suspicion it was a little too broad of a question. I'm thinking in terms of fundamentals. Independent of JSP, EE, I'm curious what most programmers need to have an intimate knowledge of without having to reference. For example, 9 out of 10 projects you've found yourself creating your own stacks instead of using built in stacks and using/enhancing those or you've had to have a firm understanding of string manipulation or using i/o etc... Essentially I'm finding myself in a position where my theortical knowledge of Java is quite firm and I'm confident in it, however I feel like I've learned words but can't make a sentence from them. Unfortunately during my studies I've found that the classes I've taken have given me peices and parts, however there seems to be a lacking in making them a cohesive unit by bringing everything together. Over the summer I'd like to concentrate on what tools programmers have found themselves most often in need of without having to reference how it's done so that I can improve my effeciency. Regards, Michael
Originally posted by siu chung man: hi michael hum.... I think depend on which situation. Which type of the project you need to do? Such as information system. If you need to do through web base,some extra knowledge you need to know. Using JSP J2EE standard,Tag library,Java Beans..etc Common knowledge of Java include String manipulation,inheritance,method overriding,overloaded method,using interface,Exception,iteration..etc Hope this help
1) Communication skills This takes effect is a number of places, but probably first on the list is understanding the language (meaning terminology and subtleties) of my customer, or whomever is giving me requirements. 2) Documentation Some would say this falls under communication, but I can't tell you the number of times people screw things up because they don't write them down. Documenting code, both embedded comments and external literature, is a key to success. 3) Knowledge of CS If you don't know the basics of OO, data structures, algorithms, etc you're programming blindfolded. 4) Ability to learn Here's the key, and why I answered your question as I did. Who cares what you know about Java? I didn't know anything about Java Collections a few months back until someone here suggested it. A google search took me to Sun's pages and a few hours later I knew how to use them. If a programmer can do that, I figure s/he can learn whats necessary as needed. If a programmer can't do it, s/he lacks the basic skills necessary to succeed. In short, your question is a little off the mark. If you're worried about which particular API to study, you're missing the forrest for the trees. As for the specifics of your question, there's no good answer. I imagine all but trivial projects do some type of either file I/O and/or DB access. But the code that does it may be only a small portion of the codebase and may not be particularly complex.
--Mark [ May 10, 2003: Message edited by: Mark Herschberg ]