is it harder to get a trading developer job in ny than chicago
- Thread starter kci
- Start date
I am doing well with job searches in NY and Chicago, and I am somewhat junior in the sense I did research in academia and not real work.
I feel the same way as you that some people come straight out of school and are very good and yet some people that have experience are not...
I am very good in C++, Java, C#, SQL.... However my observation is it seems like in the chicago job market for trading developers if you don't have 5 years or so experience, you can't even get an interview and probably won't even meet the criteria to apply for a position. Thats why I ask if its the same way in NY...
Great... we have another "straight out of college idiot" who doesn't know who he's talking to.
So here's a question:
The attached code is the user-side implementation setup for a broker I used for Forex using QuickFIX that I had 3 years ago. I was able to reduce the code to about 1/5. Tell me how I can tweak the OpenSource QuickFIX code to reduce this to 1/2....
(At this point... I haven't touched the QuickFIX source... but I tweaked the source so that I can drastically reduce the code without influencing other setup codes for other brokers...)
Please post the QuickFIX code (there's a few) and the result C# code corresponding to the tweak.
Gann,
What you are asking is unfair. You have had years to think about the problem.
Also, I looked at your code. Some of your QF code looked hacked, not engineered. One suggestion is to surround all your comments with #region OldImplememtion #endregion. That would make your code easier to read. Even that is probably messy, since if you are using source control, and good comments in the checkin, you can go back and look at why you did things the way you did, and changes you made, there. You can always tell programmers that either work on one man teams, or are egocentric and don't care about the next person tha has to maintain their code. Code should be a pleasure to read. Like a novel.
Finally, optimizations to QuickFIX in my experience (which is limited since I don't use QuickFIX) is not to optimize the client code, but to optimize the communications module.
Things like this are horribe:
Why would you hardwire code like that in an FIX client? What does 2 mean? Why are you passing four parameters instead of an object of type OrderParameters (which would then allow you to inherit for each case where the symbol representation changes)? Why use Console.WriteLine that go away when code is compiled release? Use Tracer and listeners and then you can log errors no matter what.
What you are asking is unfair. You have had years to think about the problem.
Also, I looked at your code. Some of your QF code looked hacked, not engineered. One suggestion is to surround all your comments with #region OldImplememtion #endregion. That would make your code easier to read. Even that is probably messy, since if you are using source control, and good comments in the checkin, you can go back and look at why you did things the way you did, and changes you made, there. You can always tell programmers that either work on one man teams, or are egocentric and don't care about the next person tha has to maintain their code. Code should be a pleasure to read. Like a novel.
Finally, optimizations to QuickFIX in my experience (which is limited since I don't use QuickFIX) is not to optimize the client code, but to optimize the communications module.
Things like this are horribe:
Code:
[b]public void sendNOSMarket(string symbol, string side, int size, long OrdID)[/b]
{
string[] currency;
[b]currency = symbol.Split('/');[/b]
or
if (mdupdateaction.getValue() == [b]'2'[/b])
[b]Console.WriteLine("Enter");[/b]Why would you hardwire code like that in an FIX client? What does 2 mean? Why are you passing four parameters instead of an object of type OrderParameters (which would then allow you to inherit for each case where the symbol representation changes)? Why use Console.WriteLine that go away when code is compiled release? Use Tracer and listeners and then you can log errors no matter what.