RE: Export file CSV ke database derby

[Tjong, Andreas-2]

> Gm caranya export file csv ke table di database yg ada di derby, jadi
tidak perlu entry ulang berkali kali disana

 

Bisa menggunakan Tools Pentaho (Kettle).

 

Silahkan baca ini kalau memang tertarik:
http://pentaho.phi-integration.com/#TOC-Pentaho-Data-Integration-Kettle
<http://pentaho.phi-integration.com/#TOC-Pentaho-Data-Integration-Kettle>

 

Regards,

Andreas




IMPORTANT NOTICE:
The information in this e-mail (and any attachments) is confidential. If you
are not the intended recipient, you must not use or disseminate the
information. If you have received this e-mail in error, please immediately
send notification by replying this e-mail and permanently delete the
original and any copies or printouts thereof. Although this e-mail and any
attachments are believed to be free of any virus or other defect that might
affect any computer system into which it is received and opened, it is the
responsibility of the recipient to ensure that it is virus free and no
responsibility is accepted by Avrist Assurance, for any loss or damage
arising in any way from its use.

[Adelwin, Adelwin]

Ada yang udah pernah baca?

Interesting...

Hehehe

 

The Pitfalls of Java as a First Programming Language



Because of its popularity in the context of Web applications and the
ease with which beginners can produce graphical programs, Java has
become the most widely used language in introductory programming
courses. We consider this to be a misguided attempt to make programming
more fun, perhaps in reaction to the drop in CS enrollments that
followed the dot-com bust. What we observed at New York University is
that the Java programming courses did not prepare our students for the
first course in systems, much less for more advanced ones. Students
found it hard to write programs that did not have a graphic interface,
had no feeling for the relationship between the source program and what
the hardware would actually do, and (most damaging) did not understand
the semantics of pointers at all, which made the use of C in systems
programming very challenging.

Let us propose the following principle: The irresistible beauty of
programming consists in the reduction of complex formal processes to a
very small set of primitive operations. Java, instead of exposing this
beauty, encourages the programmer to approach problem-solving like a
plumber in a hardware store: by rummaging through a multitude of drawers
(i.e. packages) we will end up finding some gadget (i.e. class) that
does roughly what we want. How it does it is not interesting! The result
is a student who knows how to put a simple program together, but does
not know how to program. A further pitfall of the early use of Java
libraries and frameworks is that it is impossible for the student to
develop a sense of the run-time cost of what is written because it is
extremely hard to know what any method call will eventually execute. A
lucid analysis of the problem is presented in [4].

We are seeing some backlash to this approach. For example, Bjarne
Stroustrup reports from Texas A & M University that the industry is
showing increasing unhappiness with the results of this approach.
Specifically, he notes the following:

I have had a lot of complaints about that [the use of Java as a first
programming language] from industry, specifically from AT&T, IBM, Intel,
Bloomberg, NI, Microsoft, Lockheed-Martin, and more. [5]

He noted in a private discussion on this topic, reporting the following:

It [Texas A&M] did [teach Java as the first language]. Then I started
teaching C++ to the electrical engineers and when the EE students
started to out-program the CS students, the CS department switched to
C++. [5]

It will be interesting to see how many departments follow this trend. At
AdaCore, we are certainly aware of many universities that have adopted
Ada as a first language because of similar concerns.

A Real Programmer Can Write in Any Language (C, Java, Lisp, Ada)



Software professionals of a certain age will remember the slogan of
old-timers from two generations ago when structured programming became
the rage: Real programmers can write Fortran in any language. The slogan
is a reminder of how thinking habits of programmers are influenced by
the first language they learn and how hard it is to shake these habits
if you do all your programming in a single language. Conversely, we want
to say that a competent programmer is comfortable with a number of
different languages and that the programmer must be able to use the
mental tools favored by one of them, even when programming in another.
For example, the user of an imperative language such as Ada or C++ must
be able to write in a functional style, acquired through practice with
Lisp and ML1, when manipulating recursive structures. This is one
indication of the importance of learning in-depth a number of different
programming languages. What follows summarizes what we think are the
critical contributions that well-established languages make to the
mental tool-set of real programmers. For example, a real programmer
should be able to program inheritance and dynamic dispatching in C,
information hiding in Lisp, tree manipulation libraries in Ada, and
garbage collection in anything but Java. The study of a wide variety of
languages is, thus, indispensable to the well-rounded programmer.

Why C Matters



C is the low-level language that everyone must know. It can be seen as a
portable assembly language, and as such it exposes the underlying
machine and forces the student to understand clearly the relationship
between software and hardware. Performance analysis is more
straightforward, because the cost of every software statement is clear.
Finally, compilers (GCC for example) make it easy to examine the
generated assembly code, which is an excellent tool for understanding
machine language and architecture.

Why C++ Matters



C++ brings to C the fundamental concepts of modern software engineering:
encapsulation with classes and namespaces, information hiding through
protected and private data and operations, programming by extension
through virtual methods and derived classes, etc. C++ also pushes
storage management as far as it can go without full-blown garbage
collection, with constructors and destructors.

Why Lisp Matters



Every programmer must be comfortable with functional programming and
with the important notion of referential transparency. Even though most
programmers find imperative programming more intuitive, they must
recognize that in many contexts that a functional, stateless style is
clear, natural, easy to understand, and efficient to boot.

An additional benefit of the practice of Lisp is that the program is
written in what amounts to abstract syntax, namely the internal
representation that most compilers use between parsing and code
generation. Knowing Lisp is thus an excellent preparation for any
software work that involves language processing.

Finally, Lisp (at least in its lean Scheme incarnation) is amenable to a
very compact self-definition. Seeing a complete Lisp interpreter written
in Lisp is an intellectual revelation that all computer scientists
should experience.

Why Java Matters



Despite our comments on Java as a first or only language, we think that
Java has an important role to play in CS instruction. We will mention
only two aspects of the language that must be part of the real
programmer's skill set:

1. An understanding of concurrent programming (for which threads
provide a basic low-level model).
2. Reflection, namely the understanding that a program can be
instrumented to examine its own state and to determine its own behavior
in a dynamically changing environment.

Why Ada Matters



Ada is the language of software engineering par excellence. Even when it
is not the language of instruction in programming courses, it is the
language chosen to teach courses in software engineering. This is
because the notions of strong typing, encapsulation, information hiding,
concurrency, generic programming, inheritance, and so on, are embodied
in specific features of the language. From our experience and that of
our customers, we can say that a real programmer writes Ada in any
language. For example, an Ada programmer accustomed to Ada's package
model, which strongly separates specification from implementation, will
tend to write C in a style where well-commented header files act in
somewhat the same way as package specs in Ada. The programmer will
include bounds checking and consistency checks when passing mutable
structures between subprograms to mimic the strong-typing checks that
Ada mandates [6]. She will organize concurrent programs into tasks and
protected objects, with well-defined synchronization and communication
mechanisms.

The concurrency features of Ada are particularly important in our age of
multi-core architectures. We find it surprising that these architectures
should be presented as a novel challenge to software design when Ada had
well-designed mechanisms for writing safe, concurrent software 30 years
ago.

 

 

Adelwin Handoyo  |  Senior Consultant - Wholesale Bank
Standard Chartered Bank
Plaza By The Park #06-00, 51 Bras Basah Road. Singapore (189554)
T : (65) 655 72441  | E adelwin.adelwin@...


This email and any attachments are confidential and may also be privileged.  If you are not the addressee, do not disclose, copy, circulate or in any other way use or rely on the information contained in this email or any attachments.  If received in error, notify the sender immediately and delete this email and any attachments from your system.  Emails cannot be guaranteed to be secure or error free as the message and any attachments could be intercepted, corrupted, lost, delayed, incomplete or amended.  Standard Chartered PLC and its subsidiaries do not accept liability for damage caused by this email or any attachments and may monitor email traffic.

 

Standard Chartered PLC is incorporated in England with limited liability under company number 966425 and has its registered office at 1 Aldermanbury Square, London, EC2V 7SB.

 

Standard Chartered Bank ("SCB") is incorporated in England with limited liability by Royal Charter 1853, under reference ZC18.  The Principal Office of SCB is situated in England at 1 Aldermanbury Square, London EC2V 7SB. In the United Kingdom, SCB is authorised and regulated by the Financial Services Authority under FSA register number 114276.

 

If you are receiving this email from SCB outside the UK, please click http://www.standardchartered.com/global/email_disclaimer.html to refer to the information on other jurisdictions.

[Frans Thamura-2]

siancai siancai, java emang legenda ;)

tapi saran gue sih sekarang dg cicak vs buaya gak kelar, kita jaulan mi java
aja ;)


--
Frans Thamura
Meruvian.
Experiential Tempation of Java and Enterprise OpenSource

Meruvian bukan hanya membuat anak SMK menjadi bisa tapi SAKTI, malah
saktinya SAKTI Mandraguna.


Mobile: [phone]
Blog & Profile: http://frans.thamura.info

We provide services to migrate your apps to Java (web), in amazing fast and
reliable.


On Wed, Nov 4, 2009 at 10:04 AM, Adelwin, Adelwin <Adelwin.Adelwin@...>wrote:

>
>
>  Ada yang udah pernah baca?
>
> Interesting…
>
> Hehehe
>
>
>
> The Pitfalls of Java as a First Programming Language
>
>  Because of its popularity in the context of Web applications and the ease
> with which beginners can produce graphical programs, Java has become the
> most widely used language in introductory programming courses. We consider
> this to be a misguided attempt to make programming more fun, perhaps in
> reaction to the drop in CS enrollments that followed the dot-com bust. What
> we observed at New York University is that the Java programming courses did
> not prepare our students for the first course in systems, much less for more
> advanced ones. Students found it hard to write programs that did not have a
> graphic interface, had no feeling for the relationship between the source
> program and what the hardware would actually do, and (most damaging) did not
> understand the semantics of pointers at all, which made the use of C in
> systems programming very challenging.
>
> Let us propose the following principle: The irresistible beauty of
> programming consists in the reduction of complex formal processes to a very
> small set of primitive operations. Java, instead of exposing this beauty,
> encourages the programmer to approach problem-solving like a plumber in a
> hardware store: by rummaging through a multitude of drawers (i.e. packages)
> we will end up finding some gadget (i.e. class) that does roughly what we
> want. How it does it is not interesting! The result is a student who knows
> how to put a simple program together, but does not know how to program. A
> further pitfall of the early use of Java libraries and frameworks is that it
> is impossible for the student to develop a sense of the run-time cost of
> what is written because it is extremely hard to know what any method call
> will eventually execute. A lucid analysis of the problem is presented in
> [4].
>
> We are seeing some backlash to this approach. For example, Bjarne
> Stroustrup reports from Texas A & M University that the industry is showing
> increasing unhappiness with the results of this approach. Specifically, he
> notes the following:
>
> I have had a lot of complaints about that [the use of Java as a first
> programming language] from industry, specifically from AT&T, IBM, Intel,
> Bloomberg, NI, Microsoft, Lockheed-Martin, and more. [5]
>
> He noted in a private discussion on this topic, reporting the following:
>
> It [Texas A&M] did [teach Java as the first language]. Then I started
> teaching C++ to the electrical engineers and when the EE students started to
> out-program the CS students, the CS department switched to C++. [5]
>
> It will be interesting to see how many departments follow this trend. At
> AdaCore, we are certainly aware of many universities that have adopted Ada
> as a first language because of similar concerns.
>
> A Real Programmer Can Write in Any Language (C, Java, Lisp, Ada)
>
>  Software professionals of a certain age will remember the slogan of
> old-timers from two generations ago when structured programming became the
> rage: Real programmers can write Fortran in any language. The slogan is a
> reminder of how thinking habits of programmers are influenced by the first
> language they learn and how hard it is to shake these habits if you do all
> your programming in a single language. Conversely, we want to say that a
> competent programmer is comfortable with a number of different languages and
> that the programmer must be able to use the mental tools favored by one of
> them, even when programming in another. For example, the user of an
> imperative language such as Ada or C++ must be able to write in a functional
> style, acquired through practice with Lisp and ML1, when manipulating
> recursive structures. This is one indication of the importance of learning
> in-depth a number of different programming languages. What follows
> summarizes what we think are the critical contributions that
> well-established languages make to the mental tool-set of real programmers.
> For example, a real programmer should be able to program inheritance and
> dynamic dispatching in C, information hiding in Lisp, tree manipulation
> libraries in Ada, and garbage collection in anything but Java. The study of
> a wide variety of languages is, thus, indispensable to the well-rounded
> programmer.
>
> Why C Matters
>
>  C is the low-level language that everyone must know. It can be seen as a
> portable assembly language, and as such it exposes the underlying machine
> and forces the student to understand clearly the relationship between
> software and hardware. Performance analysis is more straightforward, because
> the cost of every software statement is clear. Finally, compilers (GCC for
> example) make it easy to examine the generated assembly code, which is an
> excellent tool for understanding machine language and architecture.
>
> Why C++ Matters
>
>  C++ brings to C the fundamental concepts of modern software engineering:
> encapsulation with classes and namespaces, information hiding through
> protected and private data and operations, programming by extension through
> virtual methods and derived classes, etc. C++ also pushes storage management
> as far as it can go without full-blown garbage collection, with constructors
> and destructors.
>
> Why Lisp Matters
>
>  Every programmer must be comfortable with functional programming and with
> the important notion of referential transparency. Even though most
> programmers find imperative programming more intuitive, they must recognize
> that in many contexts that a functional, stateless style is clear, natural,
> easy to understand, and efficient to boot.
>
> An additional benefit of the practice of Lisp is that the program is
> written in what amounts to abstract syntax, namely the internal
> representation that most compilers use between parsing and code generation.
> Knowing Lisp is thus an excellent preparation for any software work that
> involves language processing.
>
> Finally, Lisp (at least in its lean Scheme incarnation) is amenable to a
> very compact self-definition. Seeing a complete Lisp interpreter written in
> Lisp is an intellectual revelation that all computer scientists should
> experience.
>
> Why Java Matters
>
>  Despite our comments on Java as a first or only language, we think that
> Java has an important role to play in CS instruction. We will mention only
> two aspects of the language that must be part of the real programmer’s skill
> set:
>
>    1. An understanding of concurrent programming (for which threads
>    provide a basic low-level model).
>    2. Reflection, namely the understanding that a program can be
>    instrumented to examine its own state and to determine its own behavior in a
>    dynamically changing environment.
>
> Why Ada Matters
>
>  Ada is the language of software engineering par excellence. Even when it
> is not the language of instruction in programming courses, it is the
> language chosen to teach courses in software engineering. This is because
> the notions of strong typing, encapsulation, information hiding,
> concurrency, generic programming, inheritance, and so on, are embodied in
> specific features of the language. From our experience and that of our
> customers, we can say that a real programmer writes Ada in any language. For
> example, an Ada programmer accustomed to Ada’s package model, which strongly
> separates specification from implementation, will tend to write C in a style
> where well-commented header files act in somewhat the same way as package
> specs in Ada. The programmer will include bounds checking and consistency
> checks when passing mutable structures between subprograms to mimic the
> strong-typing checks that Ada mandates [6]. She will organize concurrent
> programs into tasks and protected objects, with well-defined synchronization
> and communication mechanisms.
>
> The concurrency features of Ada are particularly important in our age of
> multi-core architectures. We find it surprising that these architectures
> should be presented as a novel challenge to software design when Ada had
> well-designed mechanisms for writing safe, concurrent software 30 years ago.
>
>
>
>
>
> *Adelwin Handoyo  |  Senior Consultant - Wholesale Bank*
> *Standard Chartered Bank*
> Plaza By The Park #06-00, 51 Bras Basah Road. Singapore (189554)
> *T* : (65) 655 72441  |* **E* adelwin.adelwin@...
>
>
>
>
> This email and any attachments are confidential and may also be privileged.  If you are not the addressee, do not disclose, copy, circulate or in any other way use or rely on the information contained in this email or any attachments.  If received in error, notify the sender immediately and delete this email and any attachments from your system.  Emails cannot be guaranteed to be secure or error free as the message and any attachments could be intercepted, corrupted, lost, delayed, incomplete or amended.  Standard Chartered PLC and its subsidiaries do not accept liability for damage caused by this email or any attachments and may monitor email traffic.
>
>
>
> Standard Chartered PLC is incorporated in England with limited liability under company number 966425 and has its registered office at 1 Aldermanbury Square, London, EC2V 7SB.
>
>
>
> Standard Chartered Bank ("SCB") is incorporated in England with limited liability by Royal Charter 1853, under reference ZC18.  The Principal Office of SCB is situated in England at 1 Aldermanbury Square, London EC2V 7SB. In the United Kingdom, SCB is authorised and regulated by the Financial Services Authority under FSA register number 114276.
>
>
>
> If you are receiving this email from SCB outside the UK, please click http://www.standardchartered.com/global/email_disclaimer.html to refer to the information on other jurisdictions.
>
>