2 ms·
Don't really think this is true. For example had quite a hard time picking up kdb+/q, and none of the tens of languages I had previously encountered really help
by smabie 5y ago
Don't really think this is true. For example had quite a hard time picking up kdb+/q, and none of the tens of languages I had previously encountered really helped much.
- deleted 5y ago[deleted]
- dnautics 5y agoyou don't suppose there's something specific about kdb/q that makes its difficulty an outlier? Excel is easy, but if you were restricted to only using the keyboard to use excel, it wouldn't be so easy anymore.
- nivertech 5y agoErlang/Elixir and kdb+/q full-time developer here. I didn't had difficulty learning kdb+/q. But that's maybe because I had an early exposure to APL (I read a chapter on it in a book as a kid). Also I had a previous work experience in HPC, data-parallel computations and vectorization/SIMD using the array-programming languages such as Matlab, Octave, R, Julia, etc. And GPU Compute using CUDA/OpenCL. The really hard to learn part of the kdb is a proprietary frameworks around it. You need them in order to develop a production-grade systems.