Granny's Programming Pearls
"inside of every large program is a small program struggling to get out"
JavaRanch.com/granny.jsp

Khaled Abolaynain

Greenhorn
+ Follow
since Aug 31, 2016
Cows and Likes
Cows
Total received
0
In last 30 days
0
Total given
0
Likes
Total received
0
Received in last 30 days
0
Total given
7
Given in last 30 days
0
Forums and Threads
Scavenger Hunt
expand Ranch Hand Scavenger Hunt
expand Greenhorn Scavenger Hunt

Recent posts by Khaled Abolaynain

Campbell Ritchie wrote:No. You will never know all the specs, and if you ever do learn them, new specs will be developed. You shou‍ld 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.



    I will start on something and see where it leads me.


    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.



    I'm thinking about a web crawler. Wish me luck!
    3 years ago
    Welcome to the discussion Jesper,

    OK, you made a really good point here. We can do the same thing in multiple ways. But now I'm letting myself to some random incidence. I always talk to myself that when creating something new, it will be the intersection of different technologies, so if I roll up my sleeves and try to master each one alone, it would be impossible by all means to even start to produce something. Maybe I should just focus on building something and stop overthinking about it!
    3 years ago
    Thanks Ritchie,

    considering the last point, I am convinced with what you are saying. My point is how you can build effective piece of software if you are not acquainted with the full stack of tools you are given. Suppose I give you 1000 ones and you say just fine, I will learn the basic 100 (or maybe less) and learn the rest as I keep going when I need them. How would you know that you would pick the right one when you need it? Even experienced developers may not have perspective of the software you are trying to make and therefore won't be able to make full judgement. I'm really confused here and don't know what to do.
    3 years ago

    Knute Snortum wrote:Maybe an example will help:. . . .



    Now I get it, thank you. Now considering me, the developer. When learning a new language, do I have to know every spec of the language? How do you decide you are ready for your next software project after learning Java? People say practice matters more than reading books and that's true. But when you learn the basics, head to your first project, for example, then stumble upon something you can’t find an answer for. Even if you find the answer, it may not be the optimal. You wouldn’t know the right tool for the job if you didn’t dig up what every tool (language spec) does.
    3 years ago

    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.



    Hi Knute,

    Even that link is filled with words. How am I supposed to read something like this?
    3 years ago

    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.



    Take this for example: https://docs.oracle.com/javase/8/

    How many people work on a thing like that? Is there content online on how the full life-cycle of this works? How do you approach this as a developer? Do you get an idea of the whole stuff when learning or search for what you need when you stumble upon a problem when coding?


    3 years ago
    I have never been a contributor before, but I just wonder how the process of documenting Java APIs work. It's horrendously horrible and large in volume. What approach do they use when producing new content? Do you use any productivity hacks or word processors? I can't Imagine how human being can write all that stuff! They would need an army. The same thing applies for other programming languages, frameworks, software as well.
    3 years ago