That's fine; as long as you're good with pseudocode for imperative programming and know some of the semantics (implementation details), you're ok.See the one thing about being a financial programmer that gets to me is that I don't stick on any one language for too long, since I use whatever language the class requires. Did some C++. Did some Java. Was able to code 4000 lines of Java in two weeks at one point last May. Now forgot most of the syntax as well.
This is a strong statement to make in an interview, because they will follow it up with a question that involves using the master theorem to solve- something even most CS majors learn and forget- and then they will ask you to prove something is NP complete. I would recommend you also practice hedging a little on the forums, too. As a former TA of three semesters for the algorithms course after yours', I can probably get away with saying, "Yes, I'm aware of that" when it comes to order-of-complexity, and handle whatever network solving, optimization, or graph problem they want to throw at me, but unless you REALLY know what you're doing, it never hurts to hedge a little.I understand the whole idea behind algorithms and Big O notation and all of that stuff (I understand what pointers do, as well), and the only thing I haven't really covered is micro-managing the memory allocation.
That's fine; that's why most IDEs have completion lines (IE: concat comes up with you type "String." in a Java IDE) these days. If you're at a firm that's still testing for that stuff, I really hope you like working with VI, Emacs, or pico.The biggest issue I have is the syntax of the program. All the time, I think in terms of "what do I want to do" but not "how do I tell this to the computer"
Again, for programming, priority #1 is algorithms and pseudocode. Priority #2 is semantics. That's 90% of it. Less than 10% depends on proper spelling and syntax.And the problem there is that either you know the syntax of that particular language, or you don't. For instance, Analytic Partners' use of SPSS really gave me a nagging feeling because I know that Google and the hedge funds use R as their statistical language (I've heard SAS as well).
1.) A lot of bozos graduate from the top-five CS schools- MIT, CMU, Stanford, Berkeley, and Illinois, and a 4.0 GPA doesn't mean anything in computer science when it comes to competence.Furthermore, another issue I have with this whole programming issue is this:
There are people out of MIT who have studied computer science and have 3.8 GPAs and the like. What the heck is someone who programmed on the side with their engineering majors going to do about holding a candle to that? At which point am I supposed to say "I didn't study computer science. I studied OR and statistics."?
2.) I've also met a lot of smart programmers who were stats majors.
3.) The biggest correlation with programming competence that I've seen is experience.
4.) Get some practice as a programmer and you'll be just fine.