Do not post please, It is Only For Me

M

mcgene4xpro

Hi All,

I have the intention to gather all the posts, that i think it is useful or having some interesting info, in this thread..

So.. Please don't post or spam this thread.

Thank you for your cooperation.

McGene
 
SH_DW

Registered: Apr 2008
Posts: 66



04-13-08 08:57 PM
The following from Mark Brown is quite true! You have quite a bit of insight in the matter.. from EXPERIENCE, no doubt!!

An intraday trader must be able to DO WHAT IS NECESSARY w/o limits on their thinking and must also have incredible PATIENCE!

Mark Brown on the reasons some intraday traders succeed..

"I believe there are a few reasons why some make it.

1. They start in a position to not need to make a living from it. The
need for steady money like a weekly paycheck will corrupt your thinking and
force you to deviate from your plan of action that was so well thought out
prior to the heat of the battle.

2. They do not need the money that they loose. The enormous amounts of
money that it requires to learn to daytrade would exceed most people's
lifetime income. What makes the number of successful daytraders so low is
that even the few who could make it, dont have enough capital to endure the
learning curve.

3. They do not give a flying _uck about anything or anyones opinions of
what the market will or might do. The very news and opinions that surround
them becomes the mortar for their brick wall of defense that protects their
completely independent thinking.

4. They do not follow the crowd, and there is no pressure on them to
conform or perform. One absolutely must not be in a position to be held
responsible for anything that you do. Total freedom from both personal and
monetary obligations are a MUST, this alone eliminates 99.9%.

5. They have incredible discipline to not buckle under pressure. They have
a perfectly clear head and understand fully what they do and how they do it.
Battle wounds and memories of defeat are more valuable to them than the
money.

6. They do not daytrade with the goal of making money. Quite the
opposite, they would be just as happy in any type of intellectual challenge
that requires the extraordinary inverted thinking and brilliance required to
win at an individualized sport.

Mark Brown"
 
marketsurfer

Registered: Apr 2002
Posts: 127



08-03-06 02:16 PM
funny !

TA has nothing to do with quant analysis. however the TA true believers will try to convince you otherwise.
 
Please if any think there is a post they found some info might be interesting in it and want to share others here.. Please do

All are welcomes.

:D
 
There are several threads on this forum discussing the issue, but most of the post are merely ideological snippets with no real substance in them. This time let's keep it professional and under the rules of Geneva Convention

There is a lot mythology surrounding C++ nowadays. Let's take a closer look at some of them. If you can add anything from your own experience, please do so.

Myth. It is hard to avoid resource leaks in C++ because of pointers, but in Java the garbage collector takes care of resource management for you. Wrong. Use RAII, smart pointers and you never need to code delete. It is so easy. Look at QuantLib, 100K lines of code and not a single delete statement. Memory leak is the easiest part of the resource management. In Java resources must be managed too (closing files, unlocking mutex etc) and Java doesn't offer anything new in that direction.

Myth It is hard to write exception safe code in C++. This one is not just wrong, but twisted marketing propaganda designed to brainwash incompetent programmers. Writing efficient and exception safe code is hard in Java too. Avoiding memory leaks is the easiest part of the problem. The hardest part is to achieve strong exception safety (commit or rollback) without sacrificing too much efficiency. The garbage collector can't help here. Again, Java doesn't offer anything new for exception safety compared to C++.

Myth C++ is low level language which uses pointers and explicit memory management. This one makes me laugh everything I hear it. C++ inherited pointers from C. Both C and C++ are high level native languages. Pointers, C-ctyle arrays and explicit memory management have their use in low level programming, but no one forces you to use them. Just use libraries, don't code delete and you won't need to manage memory explicitly.

Myth Java is better for GUI programming. Wrong. GUI programming is a whole new science on its own. Not every programmer does GUI, just like not every surgeon performs brain surgeries. Designing good GUI is more like an art, it isn't only a programming challenge. It requires the understanding of customer's needs and a lot of human engineering. Implementing well designed GUI in whatever language you choose is the easier part of the problem.

Myth It is easy to do multithreading in Java. Another propaganda B/S. C++ offers the same abstraction mechanism for multithreading as Java does and even more. Multithreading is hard on its own. Designing good parallel algorithm is hard, but implementing it in C++ is no harder than implementing it in Java.

Myth Java is easier to learn than C++. C++ syntax is to complicated . Wrong. It is true that some syntax features are more refined and elegant in Java compared to C++. But the marginal effect is minimal. Other than that Java and C++ have almost identical syntax. Java doesn't offer any new abstraction constructs compared to C++. At the same time some very useful things from C++ are missing in Java. Java folks think that taking away freedom from programmers will improve their productivity by forcing them not to use "unsafe" C++ features. But I have different opinion. No one forces you to use pointers, C-style arrays, explicit memory management, multiple and virtual inheritance. Competent programmers don't need big brothers from Java fun club to guard them against "unsafe" coding practices. They want a programming language which supports many good abstraction concepts to implement their ideas. They know that it is hard to learn how to program well, but it is easy to learn a programming language.

Myth Java is OOP out of the box. Everything is a class in Java. Another hoax. OOP is one of the programming paradigms. It complements procedural programming, doesn't replace it. OOP in Java and C++ are almost identical, except multiple inheritance, which is missing in Java.

Myth Java has many libraries. C++ doesn't. C++ programmers must code a lot of things themselves. More propaganda. Does anyone actually use all of those libraries? I suspect that most of them are slightly modified versions of the same trick. In fact, there are many more very useful C++ and C libraries out there than Java libraries. There are some widely used general purpose algorithms which serve 95% of our library needs. Both Java and C++ have them. Those libraries comprise only tiny fraction of all libraries we may ever need. The rest is specialized stuff and C++ has more of it than Java.
 
Quote from david666:

I hope you think before you type considering you said this thread is "just for me " but now you say its for everyone flip flopping like a fish out of water
More...

:D David ,, You are stupid.. and you will will stay STUPID..

Enjoy your stupidity.
 
http://www.quantnet.com/forum/threads/quantnets-best-selling-books-of-2010.5291/

What are the best-selling books that Quantnet members purchased in 2010?
The following 25 best-selling books is compiled from a list of almost 600 titles purchased as provided by Amazon where Quantnet.com is shown as a referrer. The complete list is attached here
A Primer for the Mathematics of Financial Engineering - Dan Stefanica
Solutions Manual - A Primer For The Mathematics Of Financial Engineering - Dan Stefanica
Fifty Challenging Problems in Probability with Solutions - Frederick Mosteller
Quant Job Interview Questions And Answers - Mark Joshi
A Practical Guide To Quantitative Finance Interviews - Xinfeng Zhou
My Life as a Quant: Reflections on Physics and Finance - Emanuel Derman
How I Became a Quant: Insights from 25 of Wall Street's Elite - Richard R. Lindsey
Heard on The Street: Quantitative Questions from Wall Street Job Interviews - Timothy Crack
Starting Your Career as a Wall Street Quant - Brett Jiu
Frequently Asked Questions in Quantitative Finance - Paul Wilmott
The Complete Guide to Capital Markets for Quantitative Professionals
C++ Design Patterns and Derivatives Pricing - Mark Joshi
Principles of Financial Engineering, 2nd Edition - Salih Neftci
Stochastic Calculus for Finance I: The Binomial Asset Pricing Model - Steve Shreve
Problem Solving with C++, 7th Edition - Walter Savitch
Liar's Poker - Michael Lewis
Financial Instrument Pricing Using C++ - Daniel Duffy
Stochastic Calculus for Finance II: Continuous-Time Models - Steve Shreve
The Concepts and Practice of Mathematical Finance - Mark Joshi
Nerds on Wall Street: Math, Machines and Wired Markets - David Leinweber
Liar's Poker: Rising Through the Wreckage on Wall Street (Hardcover) - Michael Lewis
Introduction to C++ for Financial Engineers: An Object-Oriented Approach - Daniel Duffy
Working the Street: What You Need to Know About Life on Wall Street - Erik Banks
An Introduction to the Mathematics of Financial Derivatives, Second Edition - Salih Neftci
Monte Carlo Methods in Financial Engineering - Paul Glasserman
 
You must log in or register to reply here.
Back
Top