Campbell Ritchie wrote:No. You will never know all the specs, and if you ever do learn them, new specs will be developed. You should program with what you know, and gradually learn more. Nobody uses 1000 tools for anything. Learn how to use ten tools and use them. We have enough experience to recognise three different ways to do something:-
1: The way I would do it. 2: A different correct way to do it. 3: A bad way to do it.Even now, beginners can hit on a new way to do things which we hadn't thought of.
Winston Gutkowski wrote:Ideally, you want to pick something that's just beyond your current capabilities, but not too far; otherwise you're likely to get frustrated. So, for example, if you haven't used databases yet, pick a reasonably simple task that uses a database to store information. Likewise with "webby" tools: start simple, and build up gradually.
Knute Snortum wrote:Maybe an example will help:. . . .
Knute Snortum wrote:Welcome to the Ranch, Khaled!
You can read about how to write Java comments that become Javadocs here.
The enormous job of documenting a large system of programs becomes a little less daunting when each programmer takes the time to document their own code.
Carey Brown wrote:Java API documentation is usually written as specially formatted text comments inserted into the Java code. A tool called javadocs will extract those comments and format them into indexed web pages. And, yes, a person actually had to write all that stuff.