Michael Angstadt wrote:For the chicks
![]()
Tejas Prathamesh wrote:Finance knowledge would be good to have, but definitely not a pre-requisite. You can gain that on the job. The technical skills required, depend on the job profile being advertised. Like any IT department, Investment banks need people to do requirement gathering & analysis, designing, programming, administration, testing and management.
Jesper Young wrote:Why I like programming (in general)... I've been playing with computers since I was about 13, we got our first computer at home, a Commodore 64, at that time. Soon after we got it I started programming on it in BASIC. I guess I like it because I have talent for technical things, and it's just fun to create something and see it work on the computer.
Professionally, I started as a C++ programmer. I liked it, but C++ is a complicated language, with pitfalls that can cause subtle, hard to trace errors, and manual memory management (no garbage collection, you have to explicitly free memory yourself, which is a major source of memory leaks and other bugs). In 1998 I first started playing with Java and I liked it, because it's simpler than C++ and you don't need to spend so much time tracing bugs with pointers. The company I worked at at that time started getting projects that involved Java, and I started on one of the first Java projects, and have been working with Java ever since.
But now Java is showing its age, it's not developing as fast anymore, and it becomes harder and harder to add new features to the language because Sun (or now Oracle) wants to keep everything backwards compatible. The last few years new programming languages that run on the JVM are becoming more and more popular, such as Groovy, JRuby, Scala and Clojure.
I'm a fan of Scala myself, participating in the Dutch Scala Enthusiasts user group.
Tejas Prathamesh wrote:Me
What do you wish to know?
Christophe Verré wrote:
How can I check API and get something from there?
If you don't learn to use the API, you'll often find yourself in troubles. Follow the following step :
1. Check the java.lang.System class.
2. Look for the "out" field. You'll see that it is a PrintStream. Click PrintStream.
3. Look for the println method. There are many overloaded println methods. In your case, you are passing an Object to it, so click the println(Object x) method.
It says :
Prints an Object and then terminate the line. This method calls at first String.valueOf(x) to get the printed object's string value, then behaves as though it invokes print(String) and then println().
4. Now check the String.valueOf method, in the String class.
It says :
Returns the string representation of the Object argument.
Returns: if the argument is null, then a string equal to "null"; otherwise, the value of obj.toString() is returned.
Rajesh Nagaraju wrote:
Check the above code, the toString1() method is not called. When you try printing an object the toString() of the particular class is called, if there is no toString method then the toString() of the Object class is called if there is no other toString() implementation in that object's hierarchy
Christophe Verré wrote:1. A new instance (anonymous) of TestA is created. It implements toString, which actually overrides the Object class toString method.
2. println is called, passing it an Object of type TestA
3. The API explains what happens from there.
Christophe Verré wrote:
but why the toString function would run???
Did you check the API ??? new TestA() creates a new instance of class TestA, which is passed to the println method. Now, what does println do ? Check the API.
Seetharaman Venkatasamy wrote:I would suggest you to go through the source code of println method .
and by the way : in your example you are overriding the toString method in annonymous class
hth
Christophe Verré wrote:
it looks more like a declaration of a constructor
A constructor ? Which class's ? Constructors have the same name as their class. Are you saying that doString looks like a constructor ?