Quant trading's most lucrative programming language (you never heard of it)
ฝัง
- เผยแพร่เมื่อ 28 พ.ค. 2024
- In today's video I interview Jeremy Lucid. Jeremy programs in one of the most niche and lucrative programming languages in the world of quantitative trading. While most have never heard of it, all large banks and cutting-edge financial institutions are demanding ever larger amounts of developers proficient in this language (despite their continued shortage). The full uncut version is available for my patrons (link below).
Instagram: / thecodingjesus
Calendly: calendly.com/coding-jesus
Patreon: / codingjesus
Email: thecodingjesus@codingjesus.com
Kdb Jobs Website plus Kdb+ Salary
kdbplusjobs.com/
Learning Kdb+ via Python
kx.com/videos/an-introduction...
Kdb+ Learning Resources:
Q for Mortals - code.kx.com/q4m3/
Kdb Whitepapers - code.kx.com/q/wp/
Q Tips Book - amzn.to/3JEmnYe
Kdb Online Courses:
dataintellect.com/solutions/o...
learninghub.kx.com/academy/
Jeremy's TH-cam Channel (LucidKDB):
Sample Interview Questions: • kdb+ Sample Interview ...
Jeremy's LinkedIn: / jeremy-lucid-609743224
00:00 video intro
00:33 introducing jeremy
01:05 what is kdb+?
03:53 why q?
05:06 what is a kdb+ developer?
08:55 what made you pursue becoming a kdb+ developer?
10:45 how does q compare to other programming languages?
12:25 where is kdb+ most impactful in quant trading?
14:20 what is a day-in-the-life look like for a kdb+ developer?
17:37 how does the role of a kdb+ developer differ from a quant dev or software engineer?
18:58 compensation
23:45 how has specializing in kdb+ impacted your career?
25:35 what will the future hold for kdb+? Is it worth learning today?
27:30 what are resources can I use to learn kdb+? - วิทยาศาสตร์และเทคโนโลยี
The language is kdb
betting on kdb too 🎲
the language is Q , the database is kdb
@@dr3w979 is the language Q or K?
thx
Kevin deBruyne?
It's KDB+
I was looking into Q n kdb back in 2018 when I completed fin trading certificates. We used python and the boilerplate setup was too cumbersome. So it makes sense. I will be la7nching a channel for it soon
Welcome back!
Apache Cassandra and Kafka can do time series and have bigger Dev networks. For ultra low latency why not C++ over kdb+ ? I can see factors like time to market and built in domain specific features would give kdb an edge. I can argue He chose kdb because he close to kc systems. I can’t see how much more simpler to run a calculateVWAP could be on q vs. c++. Reporting and integration is a plus, ok. You basically have a stack like c++, Kafka, redis, influxDB, zeromq, etc, etc. built into kdb+. That’s a plus haha
Honestly I would have to take it for a spin. Great video, glad to see coding-J is back !
everything is finance is done cause thats the way its done and investment in tech hurts bottom line. covid displayed that heavily but even in hft where tech = alpha, theyll still use shit like kdb even tho it doesnt do anything special. the high salary is just supply/demand for existing software to maintain
Theres no kdb in tier 1 or even tier 2 hfts. Kdb is for finance. Coding jesus probably works at a bank or a small tier 3+ hft
Haven’t heard of kdb before not sure if it’s open source. But if it is not - that could be the reason. If it’s supplied by a vendor then the vendor could be sued or be responsible if something goes wrong or if there’s a vulnerability. Financial orgs are usually quite strict regarding the allowed software.
Similarly no industrial stats is done with R they use SAS which is vendor supplied and supported. Regardless of R might have a bigger community and cooler features.
I'm inclined to agree with this. It's something I've independently pondered about.. but in the spirit of basic intelligence, there are a lot of leaps being made here.
Making sense is not a prerequisite for truth.
OCaml, they teach it at some elite Operations research and CS programs like Princeton and UPenn
HOLY SHIT CODING JESUS IS BACK FROM THE DEAD LET'S GOO
What Jeremy wants to say with "trust" is "legacy". Also $20k/CPU core/year. "Trust". Also $150k/year is a python/Rust dev working on API connections. Let alone sbdy specializing in an obscure tech.
love your content
i must be some array based language like APL or J or Q
they are good at processing large volumes of data efficiently
Or K by Arthur Whitney - same "family"
@@abeard1 q is just a DSL wrapper for k, so they are fundamentally the same
Hello do you think day trading futures or stocks is worth it ? Or focus should go into other things ?
If you have a few hundred thousand its worth it, otherwise no
I can't see any juniuor kdb role. If I have already some years of experince as a backend dev, how can i pivot to KDB?
probably through Kx/data intellect?
Some tech program from JPM/other ibank also provide training on kdb+
I want to learn this quant trading from the scratch.
Any pointers ?
Brush up on your maths first
void*
Sorry dad joke i know
Math., Programming, and more math. Depending on where you are in your career considering going back to school.
Take linear algebra, calculus, diffy Q. Know or learn 1 programming language really really well . Be ready to learn c++/python if not yet.
Personal being interviewed wasn’t a quant, he was a SWE.
Best way would be to get a quant internship
great content as always! by the way, would love to see more coding videos with C# as it's easier to follow along for me than C++ code.
WELL I LOVE C#
C# sucks why would he do that lol.
Why c# ? With c++ you actually see what happens. Don't run away from the sys calls, learn about what they do. Everything can be demystified
late to here, I am a kdb+ developer in a hedge funds too
My guess is O Camel ?
What on earth is that
Jane street's trading language
Ocaml* and no it’s not.
You really wouldn’t have heard of this at least I haven’t and I’ve been programming for decades
@@madimakes I actually did, at an optiver event.
Q, but same deal
The only Q i know is from Star Trek 😂
Hopeium
I guess it cant be COBOL or Fortran cause people heard of it idk
or pascal lol
It's worth view but, it could be better to mention the dark side of KDB which is known as problem with error or debugger
this guy is baked
Kdb q
It's K or KDB ( didnt watch vid yet )
Kdb stands for the K database. k is actually the language that Q is built from. Its like a wrapper around k which is easier to read
Oh Kevin De Bruyne
Nobody cares about language if you don’t have solid data & strategy
Kinda reminds me of KQL
Let me know if you want an FPGA engineer
Kevin De Bruyne Language
This is the type of comment I come for 😂
I hate that language. Only use sometimes to fetch data, but do all the processing and statistics in Python
This is not original…….you can do this in snowflake…..and Qlik replicate and Qlik compose….kindergarten stuff…..
Mean
That’s comparing Apple to Orange juice.
KX (kdb+) formed a partnership with Snowflake last year. So you can run Q vector-processing workflows in Snowflake.
@@damondanielihow? Why isn’t anyone trying to surpass Renaissance Technologies and focusing on things that seem important but probably are not important.