Good point. However, the changes are not happening only in the level of detail, but also in the logic being used.
Gone are the days when you expected yourself to do everything to the computer. As time goes and the computer learns, using AI and other techniques, the amount of effort to be given will also reduce. Have you heard of the self-evolving and self-learning robots. Maybe even webbots are a good source. You tell them once what to do, and then they just get the details (no matter what the problems are ). The point is that as knowledge grows, so does the level of computers to do thewir tasks. We have the front-end compilers now that automate the task that yu have to do, bseides giving suggestions ( in some cases)..Some are being developed but the revoltion is defnitely in the pipeline. I agree that futuire computers will be self-learning like us and as simple learning algorithms are already present and mundane tasks have alkready been automated, what is the fuss in doing them for the non-routine ones. The level of logic wrtiting and coding has gone up and less for java coders.. thansk, jd On Sat, Jul 10, 2010 at 3:21 PM, Vince O'Sullivan <[email protected]>wrote: > The existence of libraries is not relevant to the point that I'm > trying to make. > > When I first started coding, in the 1980s and in COBOL, a typical task > would be to write a program which would take input from one or more > sources, do something to it and send the output somewhere. > > These days I write primarily in Java. A typical task is to write a > program which would take input from one or more sources, do something > to it and send the output somewhere. > > Whilst I readily acknowledge that progress has been made in all sorts > or areas; the acts of specifying and coding today is more or less > identical to what it was when I started. The level of detail that I > work at is certainly unchanged. The skills used and the constructs > created now are much the same now as they were then. I still need to > specify the SQL and execute and detail when and how to extract the > results. The loops in the code go in much the same places, error > handling still has to be manually specified, etc. > > What hasn't happened was the expected evolution to the position where > you define your inputs, define your outputs and let the computer do > the rest. > > So, not only is Java the new COBOL, but Java IS COBOL. Only the > vocabulary has changed. > > On Jul 10, 9:04 am, jitesh dundas <[email protected]> wrote: > > I beg to disagree on this one. > > > > I have seen that the amount of code that we have written till date has > grown > > to a big amount. As people keep writing the same software again an again, > we > > are coming up with libraries that are reducing the LOCs that we use. > > > > Moreover, have you thought of third-party libraries that allow us to make > > calls to common functions. for e,g, HTTP EMail CLient commons library of > > Apache reduces the LOCs that we write. > > -- > You received this message because you are subscribed to the Google Groups > "The Java Posse" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<javaposse%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/javaposse?hl=en. > > -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
