Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Email address not available #1

Closed
aryakarani opened this issue Nov 11, 2021 · 8 comments
Closed

Email address not available #1

aryakarani opened this issue Nov 11, 2021 · 8 comments

Comments

@aryakarani
Copy link

Hello TM,

I wanted to reach you but the email address on your website is apparently invalid.

Thanks,
Arya.

@je-suis-tm
Copy link
Owner

Arya, sorry for the late reply, how can I help?

@aryakarani
Copy link
Author

aryakarani commented Nov 15, 2021 via email

@je-suis-tm
Copy link
Owner

Arya, I am a bit flattered by what you said but thx for the compliment.

About the repositories, obviously Rome wasn’t built in a day. What you see is years of workings. If you check the code across the timeline, you will see how bad I used to code versus now. You have to take your time and be patient to get everything right. For instance, Cathie Wood didn’t make her name before her 60s.

As for how I got there, my only advice is enthusiasm. I am genuinely passionate about what I do. That’s what motivates me to waste countless hours to try different things. Things definitely go wrong along the way. You only stick around because you are keen to see things done. It’s the only energy to keep you on a steep learning curve.

I didn’t start out with a plan. The original purpose (probably still the same) of this GitHub page was merely to document the things I did in case someday I lost touch and had to reinvent the wheel. Start with a baby step even if it sounds really stupid (like a code to compute moving average). Your coding and knowledge will improve over time and you will be more confident and capable of working on big projects.

I cannot really advise you on what to learn. Since you want to pivot to quantitative trading, you should know it still covers front office (trading quant), mid office (risk quant) and back office (research quant). Each area requires different skillsets and knowledges. Overall, you need good understanding of statistics (range from stochastic calculus to machine learning), great level of coding (more than calling functions in packages) and some basic ideas of finance (market microstructure, pricing mechanism, etc). You come from robotics background so I assume your statistics and coding should be fair. To gain more exposure to finance, there are two paths – CFA or a master degree (preferably financial mathematics or engineering). I come from stat+econ background. Some academic knowledges come in handy but many things still need to be learnt from the job.

That’s just my two cents. Good luck!

@aryakarani
Copy link
Author

aryakarani commented Nov 20, 2021 via email

@je-suis-tm
Copy link
Owner

Well, for machine learning, Andrew Ng's lecture is undisputedly the most famous. Many people including me started there so that's what I would recommend. You can snoop around my machine learning to find any additional useful algorithms Andrew Ng doesn't cover.

As for stochastic calculus, I learned it from school so I cannot really recommend a good textbook. Maybe you can try MIT open course, after all, it's MIT!
https://ocw.mit.edu/courses/sloan-school-of-management/15-450-analytics-of-finance-fall-2010/lecture-notes/MIT15_450F10_lec02.pdf

@aryakarani
Copy link
Author

aryakarani commented Nov 24, 2021 via email

@je-suis-tm
Copy link
Owner

Yeah, well, like I said, I learned a lot on the job, sorry I can't help you on this one. I would suggest you to work on a hackathon hosted by financial institutes. It may give you an idea on what you need to learn.

@aryakarani
Copy link
Author

aryakarani commented Dec 1, 2021 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants